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-2220Done

11.5.12 RECORD the `cli-v0.2.0` release — transcribe the published version and the sandbox image digests into the repository

The trio's last leg: write down what actually got published. It can only run once the artefacts EXIST, which is why it is a third card rather than a step inside the cut — a digest cannot be transcribed before it is minted.

What to build

  1. Transcribe the published sandbox image digests into packages/cli/sandbox/README.md § Published images, replacing the previous version's rows — the same act the 0.1.1 recording leg's successor performed, in the same file.
  2. Record the published npm version wherever the repo states the current release, so the docs and the registry agree.
  3. Read the digests from the REGISTRY, not from the workflow log. A build log says what a job intended to push; the registry says what a consumer will pull. Where a skopeo inspect or equivalent is available, that is the source.
  4. Verify, do not assume, that every row it replaces is stale. If a row's digest is unchanged from the previous release, say so explicitly rather than silently rewriting an identical value — an unchanged digest across a version bump is a finding, not a formatting detail.

Scope BOUNDARY

Ends at the transcription. It does NOT publish, tag or re-run any lane (11.5.11 did that). It does NOT change product code, tests or the release workflow. If a digest is missing because a lane did not actually publish what it claimed, that is a defect to report against the cut, not to paper over with a plausible-looking value.

Acceptance criteria

  • packages/cli/sandbox/README.md § Published images carries the 0.2.0 digests, each read from the registry rather than a workflow log, with the source of each stated.
  • No _no release published yet_ placeholder or stale previous-version row remains for a variant this release published.
  • The published npm version is recorded wherever the repo states the current release.
  • Any row whose digest did NOT change across the version bump is called out explicitly rather than silently rewritten.
  • The PR body links the release run and the published package page, so the transcription is auditable against its source.

Context refs

  • packages/cli/sandbox/README.md — § Published images, the table this rewrites.
  • Precedent: the 0.1.1 cut and the recording leg that followed it — same file, same shape, one version back.
  • Predecessor: 11.5.11 — the card whose recorded outcome this transcribes.
  • Story: 11.5.