Skip to content

ci: publish to npm with trusted publishing - #270

Merged
co-sic merged 1 commit into
mainfrom
pk/npm-trusted-publishing
Nov 14, 2026
Merged

co-sic merged 1 commit into
mainfrom
pk/npm-trusted-publishing

Conversation

@co-sic

@co-sic co-sic commented Nov 14, 2026

Copy link
Copy Markdown
Collaborator

The release job on main fails with EINVALIDNPMTOKEN: npm no longer accepts the NPM_TOKEN secret. The last green main run was 2025-12-09, when npm revoked classic tokens.

This switches the release job to npm trusted publishing (OIDC), matching calendar-date: it grants id-token: write and drops NPM_TOKEN.

Before merging, a trusted publisher has to be added for graphql-transform-scalars on npmjs.com (GitHub Actions, org gastromatic, repo graphql-transform-scalars, workflow main.yml). Once this is merged, the NPM_TOKEN repo secret can be deleted.

🤖 Generated with Claude Code

The NPM_TOKEN secret is no longer accepted by npm. Publish via OIDC like calendar-date.
@co-sic
co-sic merged commit e759513 into main Nov 14, 2026
6 checks passed
@co-sic
co-sic deleted the pk/npm-trusted-publishing branch November 14, 2026 10:33
@gastrobot

Copy link
Copy Markdown

🎉 This PR is included in version 2.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants