Skip to content

ci: publish to npm through trusted publishing - #50

Merged
Arlieeee merged 1 commit into
mainfrom
ci/npm-trusted-publishing
Nov 9, 2026
Merged

Arlieeee merged 1 commit into
mainfrom
ci/npm-trusted-publishing

Conversation

@Arlieeee

@Arlieeee Arlieeee commented Nov 9, 2026

Copy link
Copy Markdown
Collaborator

Publish meshy-cli and @meshy-ai/cli through npm trusted publishing (GitHub OIDC) instead of a stored npm token.

Changed

  • release.yml requests an OIDC token (id-token: write), runs in the release environment (deployments limited to main), upgrades to npm 11.5.1+ and publishes without NODE_AUTH_TOKEN. Provenance is generated automatically.

Before merging

  • Both packages have a Trusted Publisher on npmjs.com: meshy-dev/meshy-cli, workflow release.yml, environment release, "Allow npm publish" checked.

After merging

  • Run release.yml from main to publish 0.8.4, check the provenance on both packages, then remove the NPM_TOKEN repository secret.

Both packages publish through GitHub OIDC from the release environment; no npm token is stored.
@Arlieeee
Arlieeee force-pushed the ci/npm-trusted-publishing branch from 09f88bb to d962905 Compare November 9, 2026 03:51
@Arlieeee Arlieeee changed the title [MES-18014] ci: publish to npm through trusted publishing ci: publish to npm through trusted publishing Nov 9, 2026
@Arlieeee
Arlieeee merged commit 16e3f00 into main Nov 9, 2026
7 checks passed
@Arlieeee
Arlieeee deleted the ci/npm-trusted-publishing branch November 9, 2026 04:23
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