fix: update packageManager to pnpm@9.15.9 to match lockfileVersion 9.0 in pnpm-lock.yaml#4432
Open
fix: update packageManager to pnpm@9.15.9 to match lockfileVersion 9.0 in pnpm-lock.yaml#4432
Conversation
…packages/** Co-authored-by: matthew-dean <414752+matthew-dean@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix missing release PR for recent merges
fix: trigger create-release-pr on any push to master/alpha
Mar 19, 2026
Co-authored-by: matthew-dean <414752+matthew-dean@users.noreply.github.com>
Copilot
AI
changed the title
fix: trigger create-release-pr on any push to master/alpha
fix: update packageManager to pnpm@9.15.9 to match lockfileVersion 9.0 in pnpm-lock.yaml
Mar 19, 2026
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment Tip CodeRabbit can enforce grammar and style rules using `languagetool`.Configure the |
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.
Every
create-release-prworkflow run was silently failing atpnpm install --frozen-lockfile— never reaching the PR creation step — becausepackageManager: "pnpm@8.15.0"inpackage.jsonwas incompatible with thelockfileVersion: '9.0'inpnpm-lock.yaml. pnpm 8 ignores lockfile v9 entirely, then--frozen-lockfileaborts withERR_PNPM_NO_LOCKFILE. This mismatch was introduced by PR #4426 (make-dir upgrade), which regenerated the lockfile with pnpm 9 but didn't updatepackageManager.Changes
package.json— bumppackageManagerfrompnpm@8.15.0→pnpm@9.15.9. All three workflow files usepnpm/action-setup@v4without a pinned version, so they pick this up automatically.scripts/test-release-automation.js— add Section 7: a regression test that cross-checks the pnpm major version inpackageManageragainstlockfileVersioninpnpm-lock.yaml. Fails loudly if they're incompatible (e.g. lockfile v9 + pnpm 8), so this can't silently recur..github/workflows/create-release-pr.yml— remove thepaths: ['packages/**']trigger filter so the workflow fires on any push tomaster/alpha, not only commits touching package source files.🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.