Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
33 changes: 33 additions & 0 deletions devlog/_plan/260914_cost_guard_stabilization/070_delivery.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,3 +30,36 @@ The configuration reference and every locale translation change in the same pull
request as the behaviour, because a default documented in eight languages is wrong
in eight languages the moment the code lands. `structure/` ownership docs for the
affected invariants change with them.

## 2.55.0 release record

| field | value |
| --- | --- |
| product snapshot | `62f02223a0` on `dev` |
| preview SHA | `7bdd1b29b5` (`2.55.0-preview.20260914`) |
| stable SHA | `1cc89cf88c` (`2.55.0`) |
| dev next | `2.56.0` (#4618) |
| preview push CI | run 34833399886, success |
| preview service lifecycle | run 34833399853, success |
| preview dry-run / publish | 34834321705 / 34834502951, both success |
| main push CI | run 34835022788, success |
| main service lifecycle | run 34835022762, success |
| main dry-run / publish | 34836327017 / 34836498588, both success |
| registry: preview | verified, `registry.npmjs.org/@bitkyc08%2Fopencodex/2.55.0-preview.20260914` returns 200 |
| registry: stable | **pending** -- the version endpoint still returns 404 |

The preview and stable trees are byte-identical apart from `package.json.version`;
`git diff origin/preview origin/main -- . ':!package.json'` is empty.

**The stable registry line is the honest part.** The publish job reported success, its
post-publish registry smoke passed on the runner, and the `v2.55.0` tag and GitHub Release point
at `1cc89cf88c`. Fifteen minutes later the registry version endpoint still answers 404 and
`dist-tags.latest` still reads `2.54.0`, while the preview published minutes earlier answers 200.
So the receipt exists and availability is unconfirmed, which is `registryVerification: pending` --
not a missing package. Do not re-run the publish: a second dispatch against the same version is
the failure mode the bounded-read path exists to prevent. Recover the observation, then announce.

What this release does not claim: the PRD's RG2 set is not complete. The durable cross-restart
reservation ledger, V2 child first placement, the minimum quota/cache domain contract, the
transient half-open probe lease, combo hops on the shared budget, Cursor's inner retries and the
sends-per-logical-request surfacing all remain open, so #4546 stays open too.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Reconcile the conflicting #4546 closure instructions

This newly records that several RG2 requirements remain unfinished and that #4546 must stay open, but the same file still instructs the wp2/wp3 PR to use Closes #4546 and manually close the issue after landing (lines 23–25). A maintainer following that delivery section could therefore close the umbrella issue while the listed work remains untracked; update the earlier linkage to describe a partial delivery (for example, Refs #4546) and remove the manual-close instruction. Repository guidance reserves Closes for a PR that actually resolves the issue.

AGENTS.md reference: AGENTS.md:L284-L287

Useful? React with 👍 / 👎.

Loading