Add patch release script #2502
Add patch release script #2502
Conversation
|
Why a slash command instead of a script? I ask because I have some trust issues with LLMs based on experience, and feel that having code we can validate is safer and easier to reason with when something goes wrong. |
There was a problem hiding this comment.
Pull request overview
This PR adds a /patch-release Claude Code slash command that automates the scanner patch release process. The command streamlines creating patch releases by handling version detection, validation, git operations, and GitHub release creation.
Key changes:
- Auto-detection of the next patch number when not explicitly provided
- Validation checks for release commit state and sequential patch numbering
- Automated GitHub release creation with proper semantic versioning handling
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This more of an experiment rather than a suggestion on how we should manage scanner releases. These slash commands are just prompt templates, and all "judgement calls" LLM could do are scriptable here. |
|
Would this be better suited for one of the tooling repos? |
Probably. I think this is an example of AI vibe, so tooling might make more sense. I might look into converting these steps into a script, maybe using claude to do it. |
|
@BradLugo Asked Claude to convert this to a script. Can you take a look to see if it makes sense? |
jvdm
changed the title
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated 3 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Adds a `/patch-release` command that automates the scanner patch release process. The command handles: - Auto-detection of the next patch number - Validation that HEAD is not already a release commit - Sequential patch number verification - Cherry-pick prompts - GitHub release creation with proper --latest flag handling - Release documentation generation Usage: /patch-release <RELEASE> [PATCH_NUMBER] Example: /patch-release 2.36 (auto-detects next patch) 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
The LLM-based slash command has been replaced with a deterministic bash script that provides the same functionality with: - Full testability (--dry-run mode) - Auditability (every command visible in source) - Reproducibility (same input → same behavior) - Proper error handling (set -euo pipefail) Usage: ./scripts/patch-release.sh [--dry-run] [-y] <RELEASE> [PATCH_NUMBER] 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
Co-authored-by: Copilot <[email protected]>
jvdm
force-pushed
the
jvdm/claude-based-patch-release
branch
from
05524ea to
588ee26
Compare
2 participants
Summary
scripts/patch-release.shto automate the scanner patch release process--latestflag based on semantic versioningUsage
Options:
--dry-run- Preview what would happen without making changes-y, --yes- Skip confirmations (for automation)Examples:
Test plan
./scripts/patch-release.sh --dry-run 2.37to verify workflow