Skip to content

Quita el NPM_TOKEN que ya no se usa al publicar - #9

Merged
mijhaels merged 1 commit into
mainfrom
ci/remove-npm-token
Oct 12, 2026
Merged

mijhaels merged 1 commit into
mainfrom
ci/remove-npm-token

Conversation

@mijhaels

Copy link
Copy Markdown
Collaborator

Summary

 - name: Publish package
   run: npm publish
-  env:
-    NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

La 0.2.0 ya se publicó con trusted publishing (OIDC) y el secreto NPM_TOKEN está borrado, así que esta referencia apuntaba a un secreto vacío.

Evidence

  • Before: el workflow nombra secrets.NPM_TOKEN, que no existe (gh secret list vacío).
    After: npm publish se autentica solo con OIDC, igual que en la publicación de 0.2.0 (Signed provenance statement … from GitHub Actions). format:check pasa.

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

npm publishes through trusted publishing (OIDC) and the NPM_TOKEN secret
has been deleted.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mijhaels
mijhaels merged commit bf1e79d into main Oct 12, 2026
3 checks passed
@mijhaels
mijhaels deleted the ci/remove-npm-token branch October 27, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant