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

feat(projman): add SessionStart version sync check #292

Merged
lmiranda merged 1 commits from fix/issue-290-version-sync-check into development 2026-01-29 01:41:17 +00:00
Conversation 0 Commits 1 Files Changed 1 +23
lmiranda commented 2026-01-29 01:40:08 +00:00
Owner
Copy Link

Summary

Adds early detection of version drift at session start. When versions in README.md, marketplace.json, and CHANGELOG.md don't match, displays a warning and suggests /suggest-version.

Problem

Version mismatches between files (e.g., Sprint 6: main had v5.2.0 while development had v5.3.0) cause confusion and release issues. There was no proactive detection.

Solution

Added version consistency check to projman SessionStart hook:

  • Extracts versions from README.md title, marketplace.json metadata, CHANGELOG.md
  • Compares all three versions
  • Warns if mismatch detected
  • Suggests /suggest-version to analyze and fix

Test plan

  • Versions matching (5.3.0) - no warning shown
  • Simulated drift (README v5.2.0 vs others v5.3.0) - warning displayed
  • Test in fresh session with actual version drift

Issue #290 Progress

This PR addresses acceptance criteria #4:

  • SessionStart warns about version drift

Remaining criteria for future PRs:

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

Partial fix for #290

🤖 Generated with Claude Code

## Summary Adds early detection of version drift at session start. When versions in README.md, marketplace.json, and CHANGELOG.md don't match, displays a warning and suggests `/suggest-version`. ## Problem Version mismatches between files (e.g., Sprint 6: main had v5.2.0 while development had v5.3.0) cause confusion and release issues. There was no proactive detection. ## Solution Added version consistency check to projman SessionStart hook: - Extracts versions from README.md title, marketplace.json metadata, CHANGELOG.md - Compares all three versions - Warns if mismatch detected - Suggests `/suggest-version` to analyze and fix ## Test plan - [x] Versions matching (5.3.0) - no warning shown - [x] Simulated drift (README v5.2.0 vs others v5.3.0) - warning displayed - [ ] Test in fresh session with actual version drift ## Issue #290 Progress This PR addresses **acceptance criteria #4**: - [x] SessionStart warns about version drift Remaining criteria for future PRs: - [ ] Version mismatch detected before commit (PreToolUse hook) - [ ] `/sprint-close` includes version bump step (enforcement) - [ ] Release workflow works with protected branches (PR creation) Partial fix for #290 🤖 Generated with [Claude Code](https://claude.ai/code)
lmiranda added the Type/BugPriority/High labels 2026-01-29 01:40:08 +00:00
lmiranda added 1 commit 2026-01-29 01:40:09 +00:00
feat(projman): add SessionStart version sync check 7c4959fb77 
Adds early detection of version drift between README.md, marketplace.json,
and CHANGELOG.md at session start. When versions don't match, displays
a warning and suggests running /suggest-version to analyze and fix.

This addresses acceptance criteria #4 from issue #290:
- [x] SessionStart warns about version drift

Remaining criteria for future PRs:
- [ ] Version mismatch detected before commit (PreToolUse hook)
- [ ] /sprint-close includes version bump step (enforcement)
- [ ] Release workflow works with protected branches (PR creation)

Partial fix for #290

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda merged commit d457e458a8 into development 2026-01-29 01:41:17 +00:00
lmiranda deleted branch fix/issue-290-version-sync-check 2026-01-29 01:41:17 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
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 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#292
Delete Branch "fix/issue-290-version-sync-check"

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?