Skip to content

fix(release): let npm use OIDC publishing - #80

Merged
lvndry merged 1 commit into
mainfrom
fix/npm-oidc-publishing
Sep 18, 2026
Merged

lvndry merged 1 commit into
mainfrom
fix/npm-oidc-publishing

Conversation

@lvndry

@lvndry lvndry commented Sep 18, 2026

Copy link
Copy Markdown
Owner

What & why

Lets release jobs authenticate to npm through the configured GitHub Actions trusted publisher. The generated npm configuration previously supplied a placeholder classic token, preventing npm from discovering the workflow's OIDC credentials and causing publishes to fail with a misleading 404.

How to verify

  • Run a release without an NPM_TOKEN secret and confirm the platform packages and quartet-ai publish successfully.
  • Check the published package on npm and confirm its GitHub Actions provenance is present.
  • Re-run a release whose package version already exists and confirm the workflow skips it cleanly.

@vercel

vercel Bot commented Sep 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
quartet Ready Ready Preview Sep 18, 2026 10:08am UTC

@lvndry
lvndry merged commit 5c1ccad into main Sep 18, 2026
5 checks passed
@lvndry
lvndry deleted the fix/npm-oidc-publishing branch September 18, 2026 10:36

This branch was successfully deployed

1 active deployment
Preview — 596bf506 Deployed Sep 18, 2026 by vercel[bot]
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