Skip to content

chore: version bump for --continue release - #665

Merged
namastex888 merged 4 commits into
mainfrom
dev
Mar 18, 2026
Merged

namastex888 merged 4 commits into
mainfrom
dev

Conversation

@namastex888

@namastex888 namastex888 commented Mar 18, 2026 •

Copy link
Copy Markdown
Contributor

Force new version so npm publishes the --continue fix. Merge commit only.

Summary by CodeRabbit

  • Chores
    • Version configuration updated across plugin and package manifests. No functional changes or new features included in this release.

github-actions Bot and others added 4 commits March 18, 2026 13:11
…663)

Replace all `--resume <uuid>` usage with `--continue <name>` for session
resumption. Claude Code natively supports resuming sessions by their
`--name` value, making UUID-based session tracking unnecessary.

- provider-adapters: emit --continue instead of --resume
- team-lead-command: resumeSessionId → continueName
- session.ts: remove findLastSessionId JSONL scraping, use name-based continue
- genie.ts: remove session-store import, use --continue with name directly
- auto-spawn: remove lastSessionId usage from spawn args
- protocol-router: derive continue name from template (${team}-${role})
- protocol-router-spawn: resumeSessionId → continueName, update log message
- agent-registry: remove lastSessionId from WorkerTemplate
- agents.ts: remove lastSessionId from template saves
- spawn-command: emit --continue instead of --resume
- Delete session-store.ts (dead code)
- Update all tests

Wish: session-continue-by-name

Co-authored-by: Genie <genie@automagik.ai>
@coderabbitai

coderabbitai Bot commented Mar 18, 2026 •

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: f69db130-5df4-49dd-af16-2225dc48bd4a

📥 Commits

Reviewing files that changed from the base of the PR and between 73dbd91 and 53c99bd.

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

📝 Walkthrough

Walkthrough

Version number updated from 3.260318.4 to 3.260318.1 across five manifest and package configuration files for the main package and Genie plugin.

Changes

Cohort / File(s) Summary
Version Updates
.claude-plugin/marketplace.json, openclaw.plugin.json, package.json, plugins/genie/.claude-plugin/plugin.json, plugins/genie/package.json
Version field downgraded from 3.260318.4 to 3.260318.1 across all manifest and package files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev
📝 Coding Plan
  • Generate coding plan for human review comments

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 and usage tips.

@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on adjusting version numbers across various configuration and package files to ensure a specific version of the genie package is correctly published to npm. The change is crucial for releasing a fix related to the --continue feature, ensuring that users receive the intended update.

Highlights

  • Version Update: Updated the version number for the genie package and related plugin configurations from 3.260318.4 to 3.260318.1 across multiple files.
  • Release Preparation: Ensured the correct version is set to facilitate the publishing of a fix related to the --continue functionality on npm.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@namastex888
namastex888 merged commit a0a133b into main Mar 18, 2026
8 of 10 checks passed

@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 intends to perform a version bump for a new release. However, all version numbers in the changed files have been decreased from 3.260318.4 to 3.260318.1. This is a critical issue because package managers like npm require version numbers to be incremented for new publications. Decreasing the version will likely prevent the new release from being published. I have added a comment to package.json to highlight this problem.

Comment thread package.json
{
"name": "@automagik/genie",
"version": "3.260318.4",
"version": "3.260318.1",

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.

critical

The version has been decreased from 3.260318.4 to 3.260318.1. This contradicts the pull request's goal of a 'version bump' for a new release. Package managers like npm do not allow publishing a version that is lower than an already published version. To release a fix, the version number must be incremented. If 3.260318.4 is the latest published version, the next version should be higher, for example 3.260318.5.

@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: 53c99bd54d

ℹ️ 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": "3.260318.4",
"version": "3.260318.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 Keep release versions monotonic

This change lowers the published version from 3.260318.4 to 3.260318.1, which makes the new release sort as older than the previous one; in environments already on 3.260318.4, the update check path (scripts/tmux/genie-update-check.sh, lines 81–89) only advertises updates when latest_version is greater via sort -V, so users will not be prompted to upgrade to the commit that is supposed to ship the --continue fix.

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