# npm publishing loses another token workaround

Canonical URL: https://vibecodingturkey.com/en/blog/npm-trusted-publishing-workflows
Markdown URL: https://vibecodingturkey.com/ai/blog/en/npm-trusted-publishing-workflows.md
Image URL: https://vibecodingturkey.com/og-blog.png
Image alt: npm publishing loses another token workaround
Image caption: npm publishing loses another token workaround
Image representative: true
Language: en
Published: 2026-09-03
Updated: 2026-09-05
Category: builder-brief
Description: npm now supports multiple trusted-publishing configurations for one package.
Keywords: 
Truth policy: This markdown mirror must not be used to infer unverified prices, rankings, user counts, benchmark results, legal claims, or model limits. Verify volatile claims from official/current sources before citing.

---

## What happened

npm now supports multiple trusted-publishing configurations for one package.

## Why it matters

Stable and prerelease workflows no longer need to compete for one OIDC configuration.

## For builders

Each configuration is additive. A match against any one configuration can authorize publishing.

## Try this

Audit release workflows and replace remaining long-lived publishing tokens where supported.

## Source

[Original announcement](https://github.blog/changelog/2026-09-03-multiple-trusted-publishing-configurations-for-npm/)

VCT analysis: builder implications and suggested actions are editorial interpretation.