Fix npm provenance repository identity for Shield 2.1.2 - #5
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.
Npm rejected Shield 2.1.1 because its lowercase repository URL did not match the case-sensitive GitHub Actions provenance identity. Correct the URL to
https://github.com/ZeroLeaks/shield, validate that identity before publishing, and prepare 2.1.2 with matching package and registry documentation. Keep earlier source tags without rewriting them.Validation: repository identity check passes locally; full package CI covers typecheck, 1,263 tests (two optional model tests skipped), build, package contents, and isolated AI SDK 5–7 consumers and the registry example. Publishing uses the persistent
NPM_TOKENsecret in thenpmGitHub environment.