Skip to content

feat(update-nanoclaw): upgrade OneCLI gateway when its pinned version moves#2774

Merged
gavrielc merged 1 commit into
mainfrom
feat/update-nanoclaw-onecli-pin
Jun 15, 2026
Merged

feat(update-nanoclaw): upgrade OneCLI gateway when its pinned version moves#2774
gavrielc merged 1 commit into
mainfrom
feat/update-nanoclaw-onecli-pin

Conversation

@Koshkoshinsk

Copy link
Copy Markdown
Collaborator

When an update moves the onecli-gateway / onecli-cli pin in versions.json, the running OneCLI gateway/CLI must be upgraded to match — otherwise the new code can fail against the old gateway. update-nanoclaw didn't surface this, so the gateway upgrade was silently skipped.

This adds:

  • versions.json as a recognized change bucket, and
  • Step 5.5: when an onecli-gateway/onecli-cli pin moves, follow docs/onecli-upgrades.md before the service restart.

Additive only — no behavior change when the pins are unchanged.

… moves

When an update moves the onecli-gateway/onecli-cli pin in versions.json, the running gateway must be upgraded to match — otherwise the new code's @onecli-sh/sdk calls fail (404 on /v1/agents) and agents can't spawn. update-nanoclaw never detected this, so the upgrade was silently skipped. Add a conditional step that follows docs/onecli-upgrades.md before restart when the pin moves.
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.

2 participants