Repository navigation
Publica en npm con trusted publishing - #8
Merged
Merged
Conversation
The NPM_TOKEN secret no longer authorizes publishes (npm returned 404 on PUT). Grant the publish job an OIDC token and declare the repository so npm can verify the workflow and attach provenance. npm still falls back to NODE_AUTH_TOKEN while the trusted publisher is not configured. 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 publicación de 0.2.0 falló porque
NPM_TOKEN(de enero de 2024) ya no autoriza:npm error 404 Not Found - PUT https://registry.npmjs.org/tu-ruc-js-client(run).publish: permissions: contents: write + id-token: write # npm intercambia el OIDC de GitHub por un token de un solo uso package.json + "repository": "git+https://github.com/ithdev/tu-ruc-js-client.git" # npm lo exige para provenanceNode 24.21.0 trae npm 11.19.0, que ya soporta trusted publishing. Mientras no esté configurado, npm sigue usando
NODE_AUTH_TOKEN.Falta un paso de un dueño del paquete (hoy solo
seb5433), con 2FA activo:Evidence
publishfalla con 404 y no se crea ni el tag ni el release.After:
format:checkylintpasan. La publicación se valida al relanzarCI/CDdespués de configurar el trusted publisher.Merge Danger
Door: two-way
Blast Radius: Publicación
No toca el código del paquete. Una vez que funcione, conviene revocar el token viejo y borrar el secreto
NPM_TOKEN.🤖 Generated with Claude Code