Fix release job failure caused by removed npm CLI flag - #1175
Merged
Elizabeth Craig (ecraig12345) merged 3 commits intoJul 9, 2026
Conversation
Copilot
AI
changed the title
[WIP] Fix failing GitHub Actions job release
Fix release job failure caused by removed npm CLI flag
Jul 9, 2026
Elizabeth Craig (ecraig12345)
marked this pull request as ready for review
July 9, 2026 06:54
Elizabeth Craig (ecraig12345)
approved these changes
Jul 9, 2026
Member
|
Copilot run |
Contributor
Author
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.
The
releaseGitHub Actions job was failing undernpm@latestbecause a backfill audit test still passed the removed--scripts-prepend-node-pathflag. This updates the test command to use npm-compatible invocations that work with current npm releases.Root cause
packages/backfill/src/__tests__/audit.test.tsused:npm run compile --scripts-prepend-node-path && npm run side-effect --scripts-prepend-node-pathnpm@latestnow rejects that flag withEUNKNOWNCONFIG, which breaks thereleaseworkflow environment.Change
"npm run compile && npm run side-effect"Effect