chore: prepare release v0.1.1#20
Conversation
- Remove PNPM_VERSION env var from ci.yml, release.yml, codeql.yml; pnpm version now read from packageManager in package.json - Fix format-check: replace turbo format --check with pnpm exec prettier --check - Apply Prettier formatting across 18 files
Update CHANGELOG with v0.1.1 release notes covering CI fixes: - pnpm version conflict resolution - format-check command fix - Dependabot PR title check bypass - Prettier formatting pass
📝 WalkthroughWalkthroughRemoves the pinned ChangesCI Workflow Fixes
Prettier Formatting Pass
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
README.md (1)
11-11: 🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick winUpdate pnpm badge version to match
package.json.The badge still shows
10.13.1, but the PR removes the hardcoded version in favor ofpackageManager: "pnpm@10.33.4"frompackage.json. Update to10.33.4(or at least10.x) to reflect the actual version.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@README.md` at line 11, The pnpm badge in README.md is out of sync with the version declared in package.json via packageManager. Update the badge referenced by the README markdown so it matches the actual pnpm version used by the repo, ideally 10.33.4 (or at minimum a 10.x badge), and keep the badge text/URL consistent with that version.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/PULL_REQUEST_TEMPLATE.md:
- Line 32: The markdown horizontal rule in the pull request template uses a
style that violates markdownlint MD035; update the rule in the PR template to
match the existing `---` convention used elsewhere in the file. Make this change
in the template content around the horizontal rule so the markdownlint check
passes and the file stays consistent.
In `@CONTRIBUTING.md`:
- Line 64: The pnpm prerequisite in the contributing docs is out of sync with
the project’s actual package manager version. Update the pnpm requirement in
CONTRIBUTING.md to match the version declared in package.json’s packageManager
field, and keep the documentation aligned with that exact pnpm version so setup
guidance stays consistent.
In `@README.md`:
- Line 113: The pnpm prerequisite in the documentation is out of sync with the
version declared in package.json. Update the pnpm entry in README.md to match
the packageManager value (pnpm@10.33.4) so contributors see the correct required
version; use the README prerequisite table and the packageManager field as the
source of truth.
---
Outside diff comments:
In `@README.md`:
- Line 11: The pnpm badge in README.md is out of sync with the version declared
in package.json via packageManager. Update the badge referenced by the README
markdown so it matches the actual pnpm version used by the repo, ideally 10.33.4
(or at minimum a 10.x badge), and keep the badge text/URL consistent with that
version.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: e8502c27-3fc6-407a-b1a6-ada073503e84
📒 Files selected for processing (21)
.github/PULL_REQUEST_TEMPLATE.md.github/workflows/ci.yml.github/workflows/codeql.yml.github/workflows/release.yml.github/workflows/stale.ymlAGENTS.mdCHANGELOG.mdCONTRIBUTING.mdREADME.mdSECURITY.mdapps/web/app/layout.tsxapps/web/app/page.tsxapps/web/postcss.config.mjsapps/widget/app/layout.tsxapps/widget/app/page.tsxapps/widget/postcss.config.mjspackages/math/package.jsonpackages/math/src/add.tspackages/math/tsconfig.jsonpackages/ui/postcss.config.mjstsconfig.json
💤 Files with no reviewable changes (4)
- tsconfig.json
- .github/workflows/codeql.yml
- .github/workflows/stale.yml
- .github/workflows/release.yml
| - | ||
|
|
||
| --- | ||
| - *** |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Fix horizontal rule style for markdownlint compliance.
The *** rule violates MD035; the rest of this file uses ---. Align to --- to prevent lint warnings and maintain consistency.
- ***
+ ---📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - *** | |
| --- |
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 32-32: Horizontal rule style
Expected: ---; Actual: ***
(MD035, hr-style)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In @.github/PULL_REQUEST_TEMPLATE.md at line 32, The markdown horizontal rule in
the pull request template uses a style that violates markdownlint MD035; update
the rule in the PR template to match the existing `---` convention used
elsewhere in the file. Make this change in the template content around the
horizontal rule so the markdownlint check passes and the file stays consistent.
Source: Linters/SAST tools
| | Node.js | `>= 22.15.1` | | ||
| | pnpm | `>= 10.13.1` | | ||
| | Git | Latest | | ||
| | pnpm | `>= 10.13.1` | |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Update pnpm prerequisite version to match package.json.
Shows >= 10.13.1, but package.json specifies pnpm@10.33.4. Align with the actual packageManager version to prevent setup issues.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CONTRIBUTING.md` at line 64, The pnpm prerequisite in the contributing docs
is out of sync with the project’s actual package manager version. Update the
pnpm requirement in CONTRIBUTING.md to match the version declared in
package.json’s packageManager field, and keep the documentation aligned with
that exact pnpm version so setup guidance stays consistent.
| | Node.js | `>= 22.15.1` | [fnm](https://github.com/Schniz/fnm) (recommended) | | ||
| | pnpm | `>= 10.13.1` | `npm install -g pnpm` | | ||
| | Git | Latest | [git-scm.com](https://git-scm.com) | | ||
| | pnpm | `>= 10.13.1` | `npm install -g pnpm` | |
There was a problem hiding this comment.
🗄️ Data Integrity & Integration | 🟡 Minor | ⚡ Quick win
Update pnpm prerequisite version to match package.json.
The prerequisite shows >= 10.13.1, but package.json specifies pnpm@10.33.4. Align this with the actual packageManager version to prevent contributor confusion.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 113, The pnpm prerequisite in the documentation is out of
sync with the version declared in package.json. Update the pnpm entry in
README.md to match the packageManager value (pnpm@10.33.4) so contributors see
the correct required version; use the README prerequisite table and the
packageManager field as the source of truth.
1 participant
Release v0.1.1
This release fixes all CI pipeline failures introduced in v0.1.0.
Changes
Fixed
PNPM_VERSION: "10.13.1"fromci.yml,release.yml, andcodeql.yml.pnpm/action-setup@v4now reads frompackageManagerinpackage.json(pnpm@10.33.4), eliminatingERR_PNPM_BAD_PM_VERSIONon every CI run.pnpm format --check(invalid Turbo flag) withpnpm exec prettier --checkto invoke Prettier directly.if: github.actor != 'dependabot[bot]'topr-title.ymlto skip validation on automated PRs.Checklist
fix/ci-format-checkdevelopvia PR ci: remove hardcoded pnpm version and fix format-check command #19v0.1.1will be created after merge triggering the release workflowPost-merge
After merging, tag
v0.1.1will be pushed to trigger the automated release workflow.Summary by CodeRabbit
Documentation
Chores
Bug Fixes