chore: use trusted publishing for v1 releases#208
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![vercel[bot]](https://avatars.githubusercontent.com/in/8329?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Additional Suggestion:
The single combined release workflow uses tokenless npm OIDC trusted publishing, but publishing runs through pnpm pinned at 9.4.0 (via packageManager), which predates pnpm's OIDC support — so both the release and release-snapshot publish steps fail with ENEEDAUTH/E401.
tobiaslins
approved these changes
Jun 18, 2026
kakadiadarpan
added a commit
that referenced
this pull request
Jun 18, 2026
## Problem - v1 [release workflow fails](https://github.com/vercel/otel/actions/runs/27784770764/job/82218536018) in `pnpm/action-setup@v4`. - Workflow set `version: 11.8.0` while `package.json` pins `pnpm@9.4.0`. - Pushing to `v1.x` should not trigger a release automatically. ## Solution - Remove explicit pnpm action version. - Keep package manager pinned to `pnpm@9.4.0`. - Keep release jobs on Node 22. - Keep releases manual-only via `workflow_dispatch`. ## Related PR(s) - #208
kakadiadarpan
added a commit
that referenced
this pull request
Jun 19, 2026
## Problem - v1 release still uses older Changesets packages/action. - v1 trusted publishing is failing after version PR merge. ## Solution - Update `@changesets/cli` and `@changesets/changelog-github` to latest. - Pin release workflow to latest `changesets/action` tag. - Regenerate lockfile. ## Related PR(s) - #208 - #209 - #210
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
NPM_TOKEN_ELEVATED.Solution
.github/workflows/release.yml.github-apiChangesets commit mode.Related PR(s)