Files
next.orly.dev/.claude/commands/release.md
mleku ed95947971
Some checks failed
Go / build-and-release (push) Has been cancelled
Add release command and bump version to v0.35.4
- Add .claude/commands/release.md slash command for automated release
  workflow with version bumping, commit creation, tagging, and push
- Supports patch and minor version increments with proper validation
- Includes build verification step before committing
- Update settings.local.json with allowed commands from previous session
- Bump version from v0.35.3 to v0.35.4

Files modified:
- .claude/commands/release.md: New release automation command
- .claude/settings.local.json: Updated allowed commands
- pkg/version/version: Version bump to v0.35.4

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2025-12-14 19:50:13 +01:00

1.6 KiB

Release Command

Review all changes in the repository and create a release with proper commit message, version tag, and push to remotes.

Argument: $ARGUMENTS

The argument should be one of:

  • patch - Bump the patch version (e.g., v0.35.3 -> v0.35.4)
  • minor - Bump the minor version and reset patch to 0 (e.g., v0.35.3 -> v0.36.0)

If no argument provided, default to patch.

Steps to perform:

  1. Read the current version from pkg/version/version

  2. Calculate the new version based on the argument:

    • Parse the current version (format: vMAJOR.MINOR.PATCH)
    • If patch: increment PATCH by 1
    • If minor: increment MINOR by 1, set PATCH to 0
  3. Update the version file (pkg/version/version) with the new version

  4. Review changes using git status and git diff --stat HEAD

  5. Compose a commit message following this format:

    • First line: 72 chars max, imperative mood summary
    • Blank line
    • Bullet points describing each significant change
    • "Files modified:" section listing affected files
    • Footer with Claude Code attribution
  6. Stage all changes with git add -A

  7. Create the commit with the composed message

  8. Create a git tag with the new version (e.g., v0.36.0)

  9. Push to remotes (origin and gitea) with tags:

    git push origin main --tags
    git push gitea main --tags
    
  10. Report completion with the new version and commit hash

Important:

  • Do NOT push to github remote (only origin and gitea)
  • Always verify the build compiles before committing: CGO_ENABLED=0 go build -o /dev/null ./...
  • If build fails, fix issues before proceeding