Repository navigation
Add verified npm releases and trusted publishing - #4
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
1 participant
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.
Adds the release path for
@misofm/codec@0.1.0and subsequent npm trusted publications. Qualification preserves the exact tarball that passed the full consumer matrix; a separate OIDC job checks its identity and digest before publishing, and a third job verifies registry bytes and consumers.The workflow requires an explicit current-main SHA and package version, refuses existing versions in publish mode, and supports read-only verification of the initial local bootstrap. Release instructions explain npm's existing-package prerequisite for configuring trust and the absence of CI provenance on the first local publication.
Tracks #3. Codec source, Wasm assets, supported runtimes, and Effect peers are unchanged.
Validation: full package checks and packed consumer matrix, release input/artifact failure probes, workflow validation, and fresh Sol review. The GitHub CI checks repeat the native oracle, byte-identical Wasm rebuilds, and packed consumers.