lmiranda
2d51df7a42
Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2.3 KiB
2.3 KiB
description
| description |
|---|
| Release patterns, branching strategies, tagging, and pre-release versions |
Release Workflow Skill
Overview
End-to-end release workflow patterns including branching, tagging, and rollback procedures.
Release Patterns
Tag-Based Release (Simple)
Best for: small projects, continuous deployment
- Commit changes to main/development
- Update version files and changelog
- Create annotated tag:
git tag -a vX.Y.Z -m "message" - Push tag:
git push origin vX.Y.Z - CI triggers deployment from tag
Branch-Based Release (Standard)
Best for: projects with QA cycles, staged releases
- Create branch:
git checkout -b release/X.Y.Z - Update version files and changelog on branch
- QA testing on release branch
- Merge to main:
git merge release/X.Y.Z - Tag on main:
git tag -a vX.Y.Z - Merge back to development:
git merge release/X.Y.Z - Delete release branch
Git Tag Operations
Creating Tags
# Annotated tag with release notes
git tag -a vX.Y.Z -m "Release vX.Y.Z
Added:
- Feature description
Fixed:
- Bug fix description"
# Push single tag
git push origin vX.Y.Z
# Push all tags
git push origin --tags
Deleting Tags (Rollback)
# Delete local tag
git tag -d vX.Y.Z
# Delete remote tag
git push origin :refs/tags/vX.Y.Z
Pre-Release Workflow
For releases that need staged rollout:
vX.Y.Z-alpha.1— First alpha, feature incompletevX.Y.Z-alpha.2— Updated alphavX.Y.Z-beta.1— Feature complete, testingvX.Y.Z-rc.1— Release candidate, final validationvX.Y.Z— Stable release
Each pre-release tag follows the same tagging process but does not update the main changelog section.
Rollback Procedure
If Tag Not Yet Pushed
- Delete local tag
- Revert version commit
- Done
If Tag Already Pushed
- Delete remote tag
- Delete local tag
- Revert version commit
- Push revert commit
- Notify team about release revert
If Deployment Occurred
- Follow the above steps
- Trigger deployment of the previous version
- Verify rollback in production
- Post-mortem on what went wrong
Safety Rules
- Never force-push tags without explicit user confirmation
- Always create annotated tags (not lightweight)
- Include release notes in tag message
- Verify tag points to expected commit before pushing