Finding / paperclip

2026-10-13-paperclip-three-stable-releases-followed-beta-exposure-their-source-match-is-not-a-release-guarantee

Three stable releases followed beta exposure; their source match is not a release guarantee. Three stables were published after approximately 10, 4.5 and 6 days of beta exposure. The first two use the same source commit as their betas, not verified byte-identical independently built packages. The third changes releases/v2026.1012.0.md, scripts/run-vitest-stable.mjs and scripts/tests/run-vitest-stable-shard.test.mjs, leaving application source unchanged. The channel policy requires at least three beta days without promising a stable date. September 22 through October 13 version-day tag counts are 3 beta, 21 nightly and 264 canary; October 13 contributes 17 canaries. Those counts are not counts of publication timestamps. Nightly 2026.1013.0-nightly.0 ships the formerly main-only morning snapshot; canary.16 ships later changes. The later default-branch commits between canary.16 be3e614d and the end-of-window e0f30a4c snapshot remain outside those published previews at the cutoff. Three observed promotions establish neither a universal beta-to-stable identity nor a typical six-to-thirteen-day fix delivery rule.

Channel: tagged-release. Half: both. Date: 2026-10-02 to 2026-10-12; channel inventory through 2026-10-13.

Operator consequence: Pin fleet versions and read the actual stable diff and breaking changes. Beta provides an observable candidate, not a guarantee about the next release or its date. Keep package publication, source containment, observed dist-tags and moving container tags distinct when assigning channel status.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-paperclip-three-stable-releases-followed-beta-exposure-their-source-match-is-not-a-release-guarantee

Profile citations

Source links

Primary links, including exact changelog lines when available.