Repository navigation
Enable npm provenance and prepare the OIDC activation release - #15
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.
The repository is now public, so npm releases can include provenance. Remove the private-repository provenance override and explicitly require attestations in the OIDC publish job.
Prepare
@vibefield/rosetta-protocol@0.1.1and@vibefield/rosetta-room@0.1.1to activate and verify the trusted publishers. npm requires each new publisher to complete its first successful publish within two days; manual dry runs do not activate it. Update workspace references and the lockfile together. The package APIs and runtime files are unchanged.The README now describes the public repository, provenance, publisher activation, and the applied main-branch protection policy.
mainrequires an up-to-date CI passed check and a pull request, including for administrators.Validation:
npm-v0.1.1tarballs pass clean-consumer ESM, NodeNext types, DOM-free entry point, and browser/CSS build checks.Merging this PR does not publish packages. After approval, tagging its main commit
npm-v0.1.1runs all CI and publishes both verified tarballs through OIDC with provenance.