Skip to content

GhostBus v0.5.10 — release-pipeline fix (npm 12 pack shape)

Choose a tag to compare

@littlestjames82-sys littlestjames82-sys released this 11 Oct 14:41
· 47 commits to main since this release

Release-pipeline fix — and an honest gap in the record, closed.

The v0.5.8 and v0.5.9 GitHub releases were created, but their publish runs failed and never reached npm (the registry stayed at 0.5.7). This release supersedes both on npm; their release notes and the CHANGELOG carry the explanation.

Root cause: round 7's new pack-manifest gate parsed npm pack --dry-run --json assuming npm ≤ 11's array-shaped output. The publish workflow installs npm@latest before running the suite (required for Trusted Publishing) — and npm 12 changed the output to an object keyed by package name. The parser produced undefined, the check threw, the suite went red, and the publish was blocked. Local development ran npm 10/11, where the old shape still holds, so the break only appeared on the runner. The gate blocking the publish was the design working; the parser's single-shape assumption was the bug.

The fix: the parser now accepts all three shapes (array, bare object, name-keyed object) and refuses with "manifest NOT verified" if none yields a real file list. Verified against live npm 10, 11, and 12 output — same 22-file manifest each time. Assertions unchanged.

No runtime change: src/ differs from 0.5.9 only in the version constant. The round-7 supply-chain work and the round-8 final sweep + posture doc ship to npm for the first time in this version.

Verified before release: 71 checks, serverless 12/12, both demos, pack gate green under three npm majors. This release's own publish run is the end-to-end proof under the runner's npm 12.