Fix publish workflow npm upgrade in Bun repo#4239
Open
zenoachtig wants to merge 1 commit intomainfrom
Open
Conversation
|
Contributor
|
The latest updates on your projects. Learn more about Argos notifications ↗︎
|
taranvohra
approved these changes
May 6, 2026
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
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.
Summary
Revert the publish workflow's npm upgrade step back to native npm instead of using Corepack.
Why
This repository declares
packageManager: bun@1.3.7. When the publish workflow enables the npm Corepack shim, npm resolution goes through Corepack inside the repo and fails with:That prevents the Changesets publish job from running, so merged release PRs do not actually publish packages such as @gitbook/embed.
Change
In
.github/workflows/publish.yaml:replace:
with:
Bun setup remains unchanged, so the repo still uses Bun for install/build/publish orchestration. This only avoids routing npm through Corepack in a Bun-managed repo.
Validation
reproduced the Corepack failure locally with
corepack npm --versionran
bun run format