chore(release): promote dev → main — stable release of v5.260710.1 (hook injection fix) - #2537
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe release version was updated from ChangesGenie version synchronization
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Code Review
This pull request updates the version number of the genie plugin from 5.260709.2 to 5.260710.1 across multiple configuration files, including package.json, marketplace.json, and plugin.json. I have no feedback to provide on these changes.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7fd739f7d3
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| { | ||
| "name": "@automagik/genie", | ||
| "version": "5.260709.2", | ||
| "version": "5.260710.1", |
There was a problem hiding this comment.
Merge this bump from the dev branch
When this version-only promotion is merged from any branch whose GitHub merge commit message does not include /dev, the stable release job is skipped: checked .github/workflows/version.yml, where the main/homolog path is gated on both startsWith(..., 'Merge pull request') and contains(..., '/dev'). In that context .well-known/latest.json remains at 5.260709.2, so install.sh/update users keep receiving the old stable release even though these package/plugin manifests now advertise 5.260710.1. Please either merge the actual dev branch or adjust the workflow gate before relying on this bump to publish stable.
Useful? React with 👍 / 👎.
Promote dev → main — stable release of v5.260710.1
Brings the dev-channel version bump to
mainso the stable-release automation mints v5.260710.1 on the stable channel (.well-known/latest.json).What this carries:
7fd739f7 chore(version): bump to 5.260710.1 [auto-version](derived on dev when the dev release was cut). The fix code itself —f61aaf13, the hook command-injection de-shelling — is already on main via #2536; this promotion is what advances the stable channel pointer and cuts the stable GitHub release for it. Stable/latest is currently still5.260709.2.version.ymlcuts the stable release only when the merge commit onmainmatchesstartsWith('Merge pull request') && contains('/dev'). A squash or rebase merge produces a different message and would silently skip the stable release — the exact failure this PR exists to correct. Use "Create a merge commit."After merge (automatic)
mainmerge → CI →version.yml(no-bump, branch=main) → dispatchesrelease.ymlwithchannel=stablefor the existingv5.260710.1tag → publishes the stable release and advanceslatest.jsonto5.260710.1.Summary by CodeRabbit