Repository navigation
Document persistent npm authentication and improve release diagnostics - #4
Merged
Merged
Conversation
x1xhlol
changed the title
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.
Publishing retries now include npm's OIDC failure diagnostics and explicitly disable package-manager caching in the release job. Document the persistent
NPM_TOKENsecret in thenpmGitHub environment, which the existing workflow loads before publication, along with token replacement and release retry commands. Trusted publishing remains available as an alternative.The registry submission also requires the public guide queued in https://github.com/x1xhlol/zeroleaks-v2/pull/229 to pass the repository's required review and deployment. No upstream Vercel issue or PR is submitted. Full package CI validates these workflow/documentation changes.