personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Investigate versioning inconsistency - CHANGELOG.md ahead of git tags #143

New Issue
Closed
opened 2026-01-24 17:47:57 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-24 17:47:57 +00:00
Owner
Copy Link

Problem Description

During a documentation audit, a versioning inconsistency was discovered:

  • Git tags: Latest tag is v3.1.1
  • CHANGELOG.md: Had entry for 3.1.2 dated 2026-01-23 (never tagged/released)
  • marketplace.json: Was at 3.1.0 (behind actual release)
  • README.md title: Was correct at v3.1.1

This indicates the versioning workflow is not properly enforced.

Immediate Fixes Applied

  1. Updated marketplace.json version to 3.1.1
  2. Marked CHANGELOG.md 3.1.2 entry as [Unreleased]

Root Cause Investigation Needed

Analyze how versioning flows through the system.

Acceptance Criteria

  • Document current version locations and their relationships
  • Identify the root cause of the 3.1.2 CHANGELOG entry without tag
  • Propose a plan to prevent future version drift
  • Implement chosen solution
## Problem Description During a documentation audit, a versioning inconsistency was discovered: - **Git tags**: Latest tag is `v3.1.1` - **CHANGELOG.md**: Had entry for `3.1.2` dated 2026-01-23 (never tagged/released) - **marketplace.json**: Was at `3.1.0` (behind actual release) - **README.md title**: Was correct at `v3.1.1` This indicates the versioning workflow is not properly enforced. ## Immediate Fixes Applied 1. Updated marketplace.json version to 3.1.1 2. Marked CHANGELOG.md 3.1.2 entry as [Unreleased] ## Root Cause Investigation Needed Analyze how versioning flows through the system. ## Acceptance Criteria - [ ] Document current version locations and their relationships - [ ] Identify the root cause of the 3.1.2 CHANGELOG entry without tag - [ ] Propose a plan to prevent future version drift - [ ] Implement chosen solution
lmiranda commented 2026-01-24 18:09:29 +00:00
Author
Owner
Copy Link

Fix Implemented

Changes Made

  1. Created scripts/release.sh - Versioning workflow script that ensures consistency:

    • Validates [Unreleased] section in CHANGELOG
    • Updates CHANGELOG, README, and marketplace.json atomically
    • Creates commit and git tag
    • Interactive prompts for review before committing

  2. Fixed CHANGELOG.md - Consolidated all changes since v3.1.1 under [Unreleased]

  3. Updated CLAUDE.md - Comprehensive versioning documentation:

    • Version locations table
    • Development workflow (use [Unreleased])
    • Release workflow (use ./scripts/release.sh)
    • SemVer guidelines

  4. Released v3.2.0 - Using the new workflow:

    • Tag: v3.2.0
    • All 33 commits since v3.1.1 properly documented
    • Version consistent across all files

Create PR

https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/compare/development...fix/issue-143-versioning-workflow

Acceptance Criteria

  • Document current version locations and their relationships
  • Identify the root cause (CHANGELOG edited before release process)
  • Propose a plan to prevent future version drift (release script)
  • Implement chosen solution (script + docs + v3.2.0 release)
## Fix Implemented ### Changes Made 1. **Created `scripts/release.sh`** - Versioning workflow script that ensures consistency: - Validates `[Unreleased]` section in CHANGELOG - Updates CHANGELOG, README, and marketplace.json atomically - Creates commit and git tag - Interactive prompts for review before committing 2. **Fixed CHANGELOG.md** - Consolidated all changes since v3.1.1 under `[Unreleased]` 3. **Updated CLAUDE.md** - Comprehensive versioning documentation: - Version locations table - Development workflow (use `[Unreleased]`) - Release workflow (use `./scripts/release.sh`) - SemVer guidelines 4. **Released v3.2.0** - Using the new workflow: - Tag: `v3.2.0` - All 33 commits since v3.1.1 properly documented - Version consistent across all files ### Create PR https://gitea.hotserv.cloud/personal-projects/leo-claude-mktplace/compare/development...fix/issue-143-versioning-workflow ### Acceptance Criteria - [x] Document current version locations and their relationships - [x] Identify the root cause (CHANGELOG edited before release process) - [x] Propose a plan to prevent future version drift (release script) - [x] Implement chosen solution (script + docs + v3.2.0 release)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#143
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?