Skip to content

ci: publish to npm with trusted publishing instead of a token - #39

Merged
ab7z merged 1 commit into
masterfrom
publish-trusted-publishing
Oct 7, 2026
Merged

ab7z merged 1 commit into
masterfrom
publish-trusted-publishing

Conversation

@ab7z

@ab7z ab7z commented Oct 7, 2026

Copy link
Copy Markdown
Member

Summary

The release of v3.3.1 failed in the publish step with npm error 404 Not Found - PUT https://registry.npmjs.org/domrobot-client. The secret NPM_TOKEN from 2024 no longer has publish rights, and npm restricts tokens that bypass 2FA.

This change removes the token from the publish step. The workflow already has id-token: write, so npm publish authenticates with OpenID Connect through the trusted publisher configured for domrobot-client on npmjs.com (GitHub Actions, organization inwx, repository nodejs-client, workflow publish.yaml). Provenance stays.

After the merge, the release v3.3.1 is created again on master. The old release and tag were deleted because nothing was published.

@ab7z
ab7z requested a review from ddmler October 7, 2026 09:07
@ab7z
ab7z merged commit 2237708 into master Oct 7, 2026
1 check passed
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.

2 participants