Repository navigation
Qualify and release schema-browser 2.0.1 through Actions - #55
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Schema-browser 2.0.1 carries the reviewed complete license/NOTICE packaging and a qualified Actions release path. The new producer selects an exact main-ancestor source, installs frozen dependencies with Bun 1.4.2, compares two clean builds, checks committed source provenance, packs and installs offline, checks Bundler/NodeNext declarations and runs the installed example in strict-CSP Chromium.
Only after qualification passes does a separate job create the exact source tag, attach all four hash-bound assets while the release is a draft, verify GitHub asset digests, publish the immutable release and dispatch the existing main-only npm OIDC publisher with exact source/archive pins. This supplies the genuine upload needed to validate the newly configured npm trusted publisher before its expiry. Existing 2.0.0 assets, the site's installed-browser pin and the private SDK remain unchanged.
Validation: narrow independent source/custody/permission review clear; official Actionlint and Bun transpilation pass; 16 existing package/embedding/integrity/parity tests pass; real historical artifact controls accept the expected cohort and reject wrong source, extra assets and archive tampering; Rust boundaries pass with zero findings and nine negative controls. Canonical inventory was regenerated: all 578 library source, 127 Rust source and 76 Rust build-input records are identical to main, with one added active release-tooling script. The canonical check and normal hosted CI are running; actual release qualification and npm OIDC upload remain subsequent gates.