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

fix(projman): Version advisor not triggering during releases #290

New Issue
Closed
opened 2026-01-28 22:50:48 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-28 22:50:48 +00:00
Owner
Copy Link

Summary

The versioning workflow is broken. Version mismatches between README.md, CHANGELOG.md, marketplace.json, and CLAUDE.md keep happening because:

  1. /suggest-version is not automatically called during /sprint-close
  2. No hook validates version consistency before commits
  3. Release workflow tries to push directly to protected branches
  4. No automatic PR creation for releases

Problems Observed

  1. Sprint 6: Main branch had v5.2.0 while development had v5.3.0 after release
  2. Recurring: Version numbers drift between files without detection
  3. Protected branches: Release commits fail because development is protected

Required Fixes

1. Add version validation hook

  • PreToolUse hook on git commit
  • Check version consistency across: README.md title, marketplace.json, CLAUDE.md, CHANGELOG.md
  • Block commit if versions mismatch

2. Integrate /suggest-version into /sprint-close

  • Auto-run version analysis before CHANGELOG update
  • Prompt user to confirm version bump
  • Update all version locations atomically

3. Fix release workflow for protected branches

  • Create release branch automatically
  • Create PR instead of direct push
  • Provide instructions for tag creation after merge

4. Add SessionStart version check

  • Warn if versions are out of sync at session start
  • Suggest running /suggest-version or manual fix

Acceptance Criteria

  • Version mismatch detected before commit
  • /sprint-close includes version bump step
  • Release workflow works with protected branches
  • SessionStart warns about version drift
## Summary The versioning workflow is broken. Version mismatches between README.md, CHANGELOG.md, marketplace.json, and CLAUDE.md keep happening because: 1. `/suggest-version` is not automatically called during `/sprint-close` 2. No hook validates version consistency before commits 3. Release workflow tries to push directly to protected branches 4. No automatic PR creation for releases ## Problems Observed 1. **Sprint 6**: Main branch had v5.2.0 while development had v5.3.0 after release 2. **Recurring**: Version numbers drift between files without detection 3. **Protected branches**: Release commits fail because development is protected ## Required Fixes ### 1. Add version validation hook - `PreToolUse` hook on git commit - Check version consistency across: README.md title, marketplace.json, CLAUDE.md, CHANGELOG.md - Block commit if versions mismatch ### 2. Integrate `/suggest-version` into `/sprint-close` - Auto-run version analysis before CHANGELOG update - Prompt user to confirm version bump - Update all version locations atomically ### 3. Fix release workflow for protected branches - Create release branch automatically - Create PR instead of direct push - Provide instructions for tag creation after merge ### 4. Add SessionStart version check - Warn if versions are out of sync at session start - Suggest running `/suggest-version` or manual fix ## Acceptance Criteria - [ ] Version mismatch detected before commit - [ ] `/sprint-close` includes version bump step - [ ] Release workflow works with protected branches - [ ] SessionStart warns about version drift
lmiranda added the Type/BugComplexity/MediumPriority/High labels 2026-01-28 22:50:48 +00:00
lmiranda commented 2026-01-29 01:40:24 +00:00
Author
Owner
Copy Link

Phase 1 fix proposed in PR #292

This addresses acceptance criteria #4: SessionStart warns about version drift

Changes:

  • Added version consistency check to projman SessionStart hook
  • Extracts versions from README.md, marketplace.json, CHANGELOG.md
  • Warns if versions don't match
  • Suggests /suggest-version to fix

Remaining criteria (future PRs):

  • Version mismatch detected before commit (PreToolUse hook)
  • /sprint-close includes version bump step (enforcement)
  • Release workflow works with protected branches (PR creation)

Issue will remain open until all criteria are addressed.

**Phase 1 fix proposed in PR #292** This addresses **acceptance criteria #4**: SessionStart warns about version drift **Changes:** - Added version consistency check to projman SessionStart hook - Extracts versions from README.md, marketplace.json, CHANGELOG.md - Warns if versions don't match - Suggests `/suggest-version` to fix **Remaining criteria (future PRs):** - [ ] Version mismatch detected before commit (PreToolUse hook) - [ ] `/sprint-close` includes version bump step (enforcement) - [ ] Release workflow works with protected branches (PR creation) Issue will remain open until all criteria are addressed.
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 Complexity/Medium Priority/High Type/Bug
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#290
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?