release
Bump version, commit, and tag a release
Installation
Suivez les instructions du dépôt pour votre agent. Consultez les fichiers et dépendances avant l’installation.
Voir la source ↗GuidesInstructions
Release Workflow
Trigger on: "release", "bump version", "prepare release", "new version"
Instructions
When triggered, execute all steps (don't just show commands):
-
Determine version bump type from user input or ask:
-
patch(0.3.0 → 0.3.1) - bug fixes -
minor(0.3.0 → 0.4.0) - new features -
major(0.3.0 → 1.0.0) - breaking changes
-
-
Run the release script:
bun run scripts/release.ts <type> -
Stage all changes:
git add -A -
Commit with version in message:
git commit -m "chore: release v<NEW_VERSION>" -
Create annotated git tag with release notes:
git tag -a v<NEW_VERSION> -m "<RELEASE_NOTES>"Write release notes summarizing what's in this release:
- Start with version header:
v<VERSION> - <SHORT_TITLE> - Group changes under
## New Features,## Bug Fixes,## Technical, etc. - Be concise but descriptive
- Look at commits since last tag:
git log $(git describe --tags --abbrev=0)..HEAD --oneline
- Start with version header:
-
Push commits and tags:
git push && git push --tags
Example
User: "release patch" → Run script with patch → git add -A → git commit -m "chore: release v0.3.1" → git tag -a v0.3.1 -m "v0.3.1 - Bug Fixes\n\n## Bug Fixes\n- Fixed crash on startup\n- Fixed save corruption" → git push && git push --tags
Viewing Release Notes
# View tag message
git tag -l -n99 v<VERSION>
# Create GitHub release from tag
gh release create v<VERSION> --notes-from-tag
Exemples
Consultez les exemples du dépôt source.
Voir la source ↗Historique source
- Date d’indexation
- 2026-01-20
- Mise à jour de l’index
- 2026-01-28
- Branch
- main
Les dates concernent ce répertoire. Consultez le dépôt pour l’historique du code.
GitHub ↗chat Comments (0)
Sign in to join the discussion and leave a comment.
No comments yet. Be the first to share your thoughts!