Auto-bump release - #2
Merged
Merged
Conversation
Signed-off-by: Josef Karasek <karasek.jose@gmail.com>
There was a problem hiding this comment.
Pull request overview
This PR introduces a more automated, repeatable release process by adding scripts to stamp the plugin manifest version, validate/build artifacts, and optionally push a release tag—plus wiring that version-stamping into the GitHub Actions release workflow.
Changes:
- Add
scripts/set_plugin_version.pyto stamp.codex-plugin/plugin.jsonto a provided semver version. - Add
scripts/cut_release.pyto run the local release sequence (stamp → validate → build/verify → commit → tag → optional push). - Update
RELEASING.md,README.md, and.github/workflows/release-skills.ymlto reflect and support the new release flow (including CI stamping from the tag).
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| scripts/set_plugin_version.py | New helper script to stamp plugin.json version for releases/CI. |
| scripts/cut_release.py | New end-to-end local release script (commit/tag/push workflow). |
| RELEASING.md | Documents the preferred release command and updated validation/build steps. |
| README.md | Surfaces the preferred release command and references release docs. |
| .github/workflows/release-skills.yml | Stamps plugin version from tag in CI and passes expected version where needed. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
wozniakjan
approved these changes
Aug 14, 2026
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.
Suppressed comments (2)
scripts/cut_release.py:68
- This output claims a release commit was created even when the version was unchanged and no commit was made (the script explicitly handles the no-diff case). The message should be accurate in both paths.
print(f"Created release commit and tag {tag_name}")
README.md:75
- This step is labeled "Refresh the plugin cachebuster", but the command shown sets a fixed version (0.1.0). After the first run, rerunning it won’t change anything, so it won’t actually act as a cachebuster. Either adjust the text to say it's setting an example version, or make the command clearly indicate a new version should be chosen each time.
1. Refresh the plugin cachebuster:
```bash
python3 scripts/set_plugin_version.py --version 0.1.0
</details>
Comment on lines
+61
to
+65
| diff = subprocess.run(["git", "diff", "--cached", "--quiet"], check=False) | ||
| if diff.returncode == 0: | ||
| print("No plugin.json changes to commit; tagging current HEAD") | ||
| else: | ||
| git("commit", "-m", f"release: {tag_name}") |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.