Skip to content
Motir
Start free

moooon

Motir

Vibe your whole project. Bring an idea — Motir's three AI layers plan it, track it, and ship it, end to end. You're looking at Motir, built in Motir.

  • Vibe Project
  • Open Source
  • AI Agent
  • AI Loop
1
requests
0
upvotes
145
planned
1,361
shipped
Follow  — continues on app.motir.co
Request a featureAtom feed

← Motir · Work items

MOTIR-2218Done

11.5.10 Release PREP — bump `@motir/cli` to 0.2.0 and write the changelog entry for the transport migration

The first leg of the release trio: everything the release needs that a pull request can deliver. It ends at the PR — no tag, no publish.

What to build

  1. Bump packages/cli/package.json#version to 0.2.0. A minor, not a patch: the transport changed, a dependency was removed, and the CLI now refuses an incompatible server — user-visible enough that a patch would understate it, not a breaking API change for the commands themselves.
  2. The changelog / release-notes entry wherever the package records one, written for a CLI user rather than a contributor: it now speaks Motir's public REST API, output is unchanged, the agent-protocol SDK is gone, and a server older than the contract this build targets produces one clear upgrade message.
  3. Verify the lane is ready without firing it — release-cli.yml triggers on a cli-v* tag and asserts the tag version equals package.json's, so confirm the version string is exactly what the next tag will carry. The workflow also has a build-and-pack-only input; use it if a dry run is warranted.
  4. Note in the PR body that this tag ALSO fires the BYOK sandbox image build, so whoever cuts it knows two lanes will run, not one.

Scope BOUNDARY

Ends at PR opened. It does NOT push a tag, publish anything, or verify a published artefact — those need the merge and belong to 11.5.11 and 11.5.12. It does NOT change the release workflow itself; if the lane needs a fix, that is its own card. It does NOT change any product code, docs or test.

Acceptance criteria

  • packages/cli/package.json#version is 0.2.0, and nothing else in the manifest changes.
  • The release-notes entry exists, describes the change from a user's point of view, and names the removed dependency and the new upgrade message.
  • The PR body records that a cli-v0.2.0 tag will fire BOTH the npm publish and the sandbox image lane.
  • The full CLI suite and the story suite are green on this PR — this is the last gate before a version number becomes public.

Context refs

  • packages/cli/package.json — the version field; currently 0.1.1.
  • .github/workflows/release-cli.yml — the cli-v* trigger, the tag-vs-manifest version assertion, and the build-only input.
  • Precedent: the 0.1.1 prep leg — the same shape, one version back.
  • Predecessors: 11.5.7 and 11.5.8 (the gates), 11.5.9 (the description npm will show).
  • Story: 11.5.