Skip to content

Upgrade to Yarn 4.12.0 for npm trusted publishing#16

Closed
hillna wants to merge 1 commit intomainfrom
nick/yarn-4.12-upgrade
Closed

Upgrade to Yarn 4.12.0 for npm trusted publishing#16
hillna wants to merge 1 commit intomainfrom
nick/yarn-4.12-upgrade

Conversation

@hillna
Copy link

@hillna hillna commented Jan 29, 2026

Summary

  • Upgrade packageManager to yarn@4.12.0
  • Add yarn.lock and PnP files for Yarn 4 compatibility

Yarn 4.10.0+ adds OIDC authentication support for GitHub Actions and GitLab CI, enabling npm trusted publishing without long-lived tokens.

Test plan

  • CI passes

Made with Cursor

Yarn 4.10.0+ adds OIDC authentication support for GitHub Actions and
GitLab CI, enabling npm trusted publishing without long-lived tokens.

Co-authored-by: Cursor <cursoragent@cursor.com>
@hillna hillna force-pushed the nick/yarn-4.12-upgrade branch from 3dbe8a4 to 5f2a76e Compare January 29, 2026 22:50
@hillna hillna requested a review from jtbandes January 30, 2026 15:57
@jtbandes
Copy link
Member

How does this PR relate to #15? Did we want to do both? Would we still want to switch from npm to yarn if we're not using it in the workflows at all?

@defunctzombie
Copy link

I don't think we use yarn for this repo do we?

@hillna
Copy link
Author

hillna commented Feb 13, 2026

You're right, this got caught up in the cursor bulk-action and did not need to be updated.

@hillna hillna closed this Feb 13, 2026
@jtbandes jtbandes deleted the nick/yarn-4.12-upgrade branch February 18, 2026 22:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants