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

chore: release v4.1.0 with versioning workflow fix #167

Merged
lmiranda merged 2 commits from release/v4.1.0 into development 2026-01-26 15:41:35 +00:00
Conversation 0 Commits 2 Files Changed 5 +71 -8
lmiranda commented 2026-01-26 15:38:53 +00:00
Owner
Copy Link

Summary

  • Add mandatory CHANGELOG and versioning steps to /sprint-close workflow
  • Update CHANGELOG with V04.1.0 changes
  • Create v4.1.0 release (README, marketplace.json, CHANGELOG)
  • Document MCP bug #160 in Known Issues

Problem Addressed

Versioning workflow was documented in CLAUDE.md but not enforced in sprint-close.
After completing sprints, CHANGELOG was not updated and releases were not created.

Solution

  • Added "Update CHANGELOG" as mandatory step 7 in sprint-close
  • Added "Version Check" as step 8 with /suggest-version and release.sh
  • Updated orchestrator agent with CHANGELOG and version reminders

Version Updates

  • Marketplace: 4.0.0 → 4.1.0
  • projman: 3.1.0 → 3.2.0

🤖 Generated with Claude Code

## Summary - Add mandatory CHANGELOG and versioning steps to `/sprint-close` workflow - Update CHANGELOG with V04.1.0 changes - Create v4.1.0 release (README, marketplace.json, CHANGELOG) - Document MCP bug #160 in Known Issues ## Problem Addressed Versioning workflow was documented in CLAUDE.md but not enforced in sprint-close. After completing sprints, CHANGELOG was not updated and releases were not created. ## Solution - Added "Update CHANGELOG" as mandatory step 7 in sprint-close - Added "Version Check" as step 8 with /suggest-version and release.sh - Updated orchestrator agent with CHANGELOG and version reminders ## Version Updates - Marketplace: 4.0.0 → 4.1.0 - projman: 3.1.0 → 3.2.0 --- 🤖 Generated with [Claude Code](https://claude.ai/code)
lmiranda added 2 commits 2026-01-26 15:38:53 +00:00
fix(projman): add mandatory CHANGELOG and versioning to sprint-close workflow 28c9552d1d 
Problem: Version workflow was documented but not enforced in sprint-close.
After completing sprints, CHANGELOG wasn't updated and releases weren't created.

Solution:
- Add "Update CHANGELOG" as mandatory step 7 in sprint-close
- Add "Version Check" as step 8 with /suggest-version and release.sh
- Update orchestrator agent with CHANGELOG and version reminders
- Add V04.1.0 wiki workflow changes to CHANGELOG [Unreleased]
- Document MCP bug #160 in Known Issues

This ensures versioning workflow is part of the sprint close process,
not just documented in CLAUDE.md.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
chore: release v4.1.0 834cf3ac56
lmiranda merged commit 61a3b4611f into development 2026-01-26 15:41:35 +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
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#167
Delete Branch "release/v4.1.0"

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?