Repository navigation
Quita el NPM_TOKEN que ya no se usa al publicar - #9
Merged
Merged
Conversation
npm publishes through trusted publishing (OIDC) and the NPM_TOKEN secret has been deleted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Summary
La 0.2.0 ya se publicó con trusted publishing (OIDC) y el secreto
NPM_TOKENestá borrado, así que esta referencia apuntaba a un secreto vacío.Evidence
secrets.NPM_TOKEN, que no existe (gh secret listvacío).After:
npm publishse autentica solo con OIDC, igual que en la publicación de 0.2.0 (Signed provenance statement … from GitHub Actions).format:checkpasa.Merge Danger
Door: two-way
Blast Radius: Publicación
Si se desconfigura el trusted publisher en npm, la próxima publicación falla en lugar de intentar con un token.
🤖 Generated with Claude Code