| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Warning .coderabbit.yaml has a parsing errorThe CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file. 💥 Parsing errors (1)Validation error: Invalid option: expected one of "off"|"warning"|"error" at "reviews.pre_merge_checks.docstrings.mode"
WalkthroughThe pnpm package manager version pin in package.json is updated, and pnpm-workspace.yaml removes the pmOnFail: download block so the trust policy section follows the remaining settings. Changespnpm toolchain settings
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Poem🚥 Pre-merge checks | ✅ 5 ✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
There was a problem hiding this comment.
Upgrades the repository’s pinned pnpm version to 11.9.0 and removes a previously-needed pmOnFail: download workaround from the pnpm workspace configuration.
Changes:
Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pnpm-workspace.yaml | Removes the pmOnFail: download workaround configuration. |
| pnpm-lock.yaml | Updates lock metadata and package-manager dependency entries for pnpm 11.9.0. |
| package.json | Updates devEngines.packageManager.version to pnpm 11.9.0 (with integrity). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
| pnpm@11.9.0: | ||
| resolution: {integrity: sha512-vWgtXQP+Ul73yf1ngMaITR51asTJyf4AxTh4KCQxDc+Q493E9Tg18G3669UIXkGFXgvLs7YN4qxburieUDbwOw==} | ||
| engines: {node: '>=22.13'} | ||
| hasBin: true |
There was a problem hiding this comment.
engines.node would pass this requirement on to consumers, which do not have to run the pnpm version in the package
so I would skip this
Sorry, something went wrong.
|
@coderabbitai did I fix the parsing error? if yes, maybe you can update your comment above |
Sorry, something went wrong.
|
Tip For best results, initiate chat on the files or code changes. 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== PR metadata =="
gh pr view 957 --repo sql-formatter-org/sql-formatter --json number,title,headRefName,baseRefName,url
echo
echo "== Review comments by coderabbitai =="
gh api repos/sql-formatter-org/sql-formatter/pulls/957/comments --paginate \
--jq '.[] | select(.user.login=="coderabbitai") | {id, path, line, body, html_url}'
echo
echo "== Issue comments mentioning parsing by coderabbitai or user =="
gh api repos/sql-formatter-org/sql-formatter/issues/957/comments --paginate \
--jq '.[] | select((.user.login=="coderabbitai" or .user.login=="karlhorky") and (.body|test("parsing|parse"; "i"))) | {user: .user.login, body, html_url}'
echo
echo "== package.json excerpt =="
sed -n '1,120p' package.json
echo
echo "== pnpm-workspace.yaml =="
sed -n '1,120p' pnpm-workspace.yamlLength of output: 6038 @karlhorky Yes — based on the current PR state, the parsing issue looks fixed. The pmOnFail: download block is gone from pnpm-workspace.yaml, and the file now looks syntactically clean. The package.json change also looks fine from what I checked. One note: GitHub didn’t return any active coderabbitai review comments on this PR, so I don’t see a specific inline comment I can update/resolve right now. If you want, I can re-review the PR from the current state. |
Sorry, something went wrong.
|
Tip For best results, initiate chat on the files or code changes. 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== PR review comments mentioning parsing or pnpm-workspace =="
gh api repos/sql-formatter-org/sql-formatter/pulls/957/comments --paginate \
--jq '.[] | select((.user.login=="coderabbitai") and ((.body|ascii_downcase|contains("parsing")) or (.path=="pnpm-workspace.yaml") or (.body|ascii_downcase|contains("yaml")))) | {id: .id, path: .path, line: .line, body: .body, url: .html_url}'
echo
echo "== Current pnpm-workspace.yaml =="
nl -ba pnpm-workspace.yaml | sed -n '1,120p'
echo
echo "== Current package.json package manager section =="
rg -n -C2 '"packageManager"|"devEngines"' package.json || trueLength of output: 1114 🏁 Script executed: #!/bin/bash
set -euo pipefail
echo "== Repo root files matching pnpm-workspace.yaml =="
fd -a '^pnpm-workspace\.yaml$' .
echo
echo "== Current pnpm-workspace.yaml =="
cat -n pnpm-workspace.yaml | sed -n '1,120p'
echo
echo "== Current package.json devEngines/packageManager section =="
cat -n package.json | sed -n '1,120p' | rg -n -C2 'devEngines|packageManager|11\.9\.0|11\.0\.8' || true
echo
echo "== PR review comments by coderabbitai on PR `#957` =="
gh api repos/sql-formatter-org/sql-formatter/pulls/957/comments --paginate \
--jq '.[] | select(.user.login=="coderabbitai") | {id: .id, path: .path, line: .line, body: .body, url: .html_url}'
echo
echo "== PR issue comments by coderabbitai on PR `#957` =="
gh api repos/sql-formatter-org/sql-formatter/issues/957/comments --paginate \
--jq '.[] | select(.user.login=="coderabbitai") | {id: .id, body: .body, url: .html_url}'Length of output: 2142 @karlhorky Yes — from what I can see, the parsing issue looks fixed now. pnpm-workspace.yaml currently has valid-looking YAML structure, and the earlier pmOnFail: download block is gone, so I don't see any remaining syntax there that would obviously trigger a parser error. |
Sorry, something went wrong.
There was a problem hiding this comment.
Looks good.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Upgrade to pnpm@11.9.0 and remove pmOnFail: download workaround: