Skip to content

ci: unblock changesets publish from npm's devEngines check #396

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kraenhansen merged 2 commits into from
Aug 11, 2026
Merged

ci: unblock changesets publish from npm's devEngines check #396

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1f5c18a
ci: unblock changesets publish from npm's devEngines check
claude Aug 11, 2026
c0596f9
ci: point the devEngines workaround comment at the upstream fix
claude Aug 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions .github/workflows/release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,3 +56,14 @@ jobs:
publish: pnpm run release
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
# Changesets shells out to `npm info` (there is no pnpm equivalent it
# can use) to determine what is already published. npm ≥ 11 checks the
# root package.json's "devEngines" on every command and errors with
# EBADDEVENGINES because we require pnpm as the package manager, which
# fails the publish before it starts. Passing force downgrades that
# check to a warning; the actual publishing still runs through
# `pnpm publish`. Changesets v3 fixes this properly by running
# `pnpm info` when pnpm is detected, but it needs changesets/action v2
# to go with it and both are prereleases for now — remove this once we
# upgrade to those.
npm_config_force: true
Loading