Uh oh!
There was an error while loading. Please reload this page.
chore(ci): remove NODE_AUTH_TOKEN once OIDC trusted publishing is enabled - #135
Conversation
Stack: npm-publishing-fixes Part of a stacked PR chain. Do not merge manually. |
bad8910 to
49ee738Compare709cdd8 to
eb7ba96Compare49ee738 to
62b2b43Compareeb7ba96 to
26e0afdCompare62b2b43 to
111830bCompare5ea4dbb to
7d8511fCompare111830b to
9502bf6Compare7d8511f to
f031159Compare9502bf6 to
c6df875Comparec6df875 to
830c98aComparef031159 to
31f96b0Compare830c98a to
4ae3d0eCompareNo actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
✅ Files skipped from review due to trivial changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughConsolidates CI workflows by deleting Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
dominic-clerk
commented
Apr 10, 2026
I have added a commit combining both release workflows ( Here's the claude summary of the changes What changed:
No behavioral changes to any of the three release channels (stable, canary, snapshot). |
It is required to configure trusted publishing
49b74e1 to
f9175f6CompareUh oh!
There was an error while loading. Please reload this page.
Removes
NODE_AUTH_TOKENfrom all three npm publish jobs now that OIDC trusted publishing is configured for the package on npmjs.com.Affects:
publish-npm(stable release)canary-publish-npm(canary release)publish(snapshot release)