Skip to content

chore(release): promote dev → main — stable release of v5.260710.1 (hook injection fix) - #2537

Merged
namastex888 merged 1 commit into
mainfrom
dev
Jul 10, 2026
Merged

namastex888 merged 1 commit into
mainfrom
dev

Conversation

@namastex888

@namastex888 namastex888 commented Jul 10, 2026 •

Copy link
Copy Markdown
Contributor

Promote dev → main — stable release of v5.260710.1

Brings the dev-channel version bump to main so 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 still 5.260709.2.

⚠️ Merge with a MERGE COMMIT — not squash, not rebase

version.yml cuts the stable release only when the merge commit on main matches startsWith('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)

main merge → CI → version.yml (no-bump, branch=main) → dispatches release.yml with channel=stable for the existing v5.260710.1 tag → publishes the stable release and advances latest.json to 5.260710.1.

Summary by CodeRabbit

  • Release
    • Updated the Genie plugin and package to version 5.260710.1.
    • Synchronized version information across marketplace, plugin, and package metadata.

@coderabbitai

coderabbitai Bot commented Jul 10, 2026 •

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: eb5390f5-4b1e-458a-88cc-6577a22ffd5f

📥 Commits

Reviewing files that changed from the base of the PR and between 00bb781 and 7fd739f.

📒 Files selected for processing (4)
  • .claude-plugin/marketplace.json
  • package.json
  • plugins/genie/.claude-plugin/plugin.json
  • plugins/genie/package.json

📝 Walkthrough

Walkthrough

The release version was updated from 5.260709.2 to 5.260710.1 across the root package, plugin package, marketplace entry, and plugin manifest.

Changes

Genie version synchronization

Layer / File(s) Summary
Release version metadata
.claude-plugin/marketplace.json, package.json, plugins/genie/.claude-plugin/plugin.json, plugins/genie/package.json
Updates all four Genie version fields to 5.260710.1.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title matches the PR’s main change: promoting dev to main for the stable release of v5.260710.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 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".

Comment thread package.json
{
"name": "@automagik/genie",
"version": "5.260709.2",
"version": "5.260710.1",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge 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 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant