Skip to content

docs(release): 0.19.0 released; Open VSX check reads the universal package at its own address - #258

Merged
RandyNorthrup merged 4 commits into
mainfrom
docs/0.19.0-released
Oct 22, 2026
Merged

RandyNorthrup merged 4 commits into
mainfrom
docs/0.19.0-released

Conversation

@RandyNorthrup

Copy link
Copy Markdown
Owner

Records the 0.19.0 release and fixes the one check that went red in its release run.

The release

v0.19.0 on 4e09cab6ea (PR #257's merge), release run 39720213044.

  • Succeeded: tag checks, reuse of CI run 39716712837's verified packages, the GitHub Release (46 assets), Marketplace, npm.
  • Failed: the Open VSX job failed at its own check, not at publishing.
    • Cause: once a version has targeted packages, Open VSX's untargeted /<version> answer names whichever package it picks (win32-arm64 to the script), so the universal VSIX was compared with another target's bytes.
    • Open VSX state: every package was uploaded, and three activated a few minutes later.
  • Checked after the run, by each target's own address:
    • all 7 packages on the Marketplace and on Open VSX match the release assets (14 of 14);
    • npm's integrity equals the release tarball's;
    • the assets pass SHA256SUMS.

The fix

scripts/publish-registry.mjs reads /api/<ns>/<ext>/universal/<version> for the untargeted package. That address also answers for versions published only universal (0.18.2).

Drill against the real Open VSX, in docs/certification/cifinal0190.md §21:

  • the tag's check fails 3 of 3 on the universal VSIX;
  • the fixed one matches 3 of 3, and still matches win32-x64.

Also

  • PLAN §10 0.19.0 released record; roadmap regenerated.
  • Windows real-use record for the release (docs/real-life/release-0.19.0-limits-W.md): 5 calls, every one muse-spark-1.3-contributor, $0.00.
  • Two closed §7 gate records archived (byte-identical reassembly, docs/certification/plan-archive.md), so the record fits under check:plan's gate.

Local: all 19 static gates exit 0; publishRegistry.test.mjs + manifest.test.ts 44/44; plan suites 135/135.

🤖 Generated with Claude Code

…package at its own address

PLAN section 10 records the 0.19.0 release (tag v0.19.0 on 4e09cab,
release run 39720213044): the GitHub Release, Marketplace and npm
published; the Open VSX job failed at its own check, because once a
version has targeted packages Open VSX's untargeted /<version> answer
names whichever package it picks (win32-arm64 to the script), so the
universal VSIX was compared with another target's bytes. Every package was
uploaded; checked by each target's own address after the run, all seven on
the Marketplace and on Open VSX match the release assets, npm's integrity
equals the release tarball and the assets pass SHA256SUMS.

The check now reads /universal/<version> (scripts/publish-registry.mjs).
Drill against the real Open VSX: the tag's check fails 3 of 3 on the
universal VSIX, the fixed one matches 3 of 3 and still matches win32-x64
(docs/certification/cifinal0190.md section 21).

Also: the Windows real-use record for the release
(docs/real-life/release-0.19.0-limits-W.md: 5 calls, every one
muse-spark-1.3-contributor, $0.00), the roadmap regenerated for the
release, and two closed section 7 gate records archived to make room for
the record (docs/certification/plan-archive.md).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 22, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review 🔄 Running since 2026-10-22T04:27:52.354631Z c7bdd3e PR opened
🔒 Security Review ✅ Completed 2026-10-22T04:30:23.874771Z c7bdd3e PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

RandyNorthrup and others added 3 commits October 21, 2026 21:49
… went through

PR #258's first run failed in posixVaultPanelFlow on hosted macOS: after
Unlock the panel still read "locked" when the step's wait ended, with no
toast and no log, in product code that was green on every macOS shard of
PR #257. The message now adds how many frames the panel published and its
last states, so a repeat shows whether the step ever ran
(docs/certification/cifinal0190.md section 22).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…utdown signal

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
PR #258's third run failed on hosted Windows only: windowsBrokerClient's
beforeAll, which builds the helpers with the person's own C# compiler, ran
past the 30 s hook budget. Owner's rule (2026-10-16): no limit of ours that
is not about a model. The seven vault suites whose setup builds or stages
native helpers or starts a broker run it with no time limit; the five
Windows suites pass here (14 tests).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@RandyNorthrup
RandyNorthrup merged commit 0cab9f3 into main Oct 22, 2026
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant