chore(deps): upgrade 23 packages to latest#81
Conversation
Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
🦋 Changeset detectedLatest commit: 19b5679 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Co-Authored-By: Claude <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThis PR updates multiple dependency version ranges across the monorepo: root devDependencies, workspace catalog entries, and package-level dependencies in packages/cli, packages/config, packages/core, and packages/ui. It adds a new Changesets file and tightens TypeScript typings in several Vitest mocks within test files. No exported/public API declarations were changed. Changes
Estimated code review effort1 (Trivial) — ~3 minutes Possibly related PRs
Poem🐰 Hops of versions, patches neat, dependencies dance to a newer beat. 🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@extensions/vscode/package.json`:
- Line 32: The devDependency "@types/vscode" version (^1.115.0) no longer
matches the declared minimum VS Code engine ("engines.vscode": "^1.110.0"),
risking use of type definitions for APIs not available at runtime; fix by either
downgrading the "@types/vscode" entry to a version that aligns with the engine
floor (match the minor/major to 1.110.x) or update the "engines.vscode" field to
"^1.115.0" (or higher) to raise the supported VS Code minimum—modify the
package.json entries for "@types/vscode" and/or "engines.vscode" accordingly so
they are consistent.
In `@packages/cli/package.json`:
- Line 54: The package.json updates React to ^19.2.5 but leaves `@types/react` at
^19.1.0; update the `@types/react` dependency version to match the runtime (e.g.,
^19.2.5) so type definitions align with the bumped React version—modify the
"@types/react" entry in package.json to the new semver and run install/lockfile
update to keep types and runtime in sync.
In `@packages/ui/package.json`:
- Around line 78-79: Update the peerDependencies React version floor to match
the dev/dependency bump: change the peerDependencies entries for "react" and
"react-dom" currently set to "^19.2.4" to "^19.2.5" so the displayed peer range
aligns with the dependencies lines `"react": "^19.2.5"` and `"react-dom":
"^19.2.5"`.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3954caaf-0824-4152-899c-5e7857b7e5ab
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml,!pnpm-lock.yaml
📒 Files selected for processing (7)
extensions/vscode/package.jsonpackage.jsonpackages/cli/package.jsonpackages/config/package.jsonpackages/core/package.jsonpackages/ui/package.jsonpnpm-workspace.yaml
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/upgrade-deps.md:
- Around line 1-2: The changeset only contains empty YAML frontmatter (---) and
no package entries or release notes, so it won't trigger version bumps or
changelog generation; update the YAML frontmatter to list each affected package
with its bump type (patch/minor/major) and add a markdown description below the
frontmatter explaining the changes, ensuring package names and bump types are
correct and reflect the PR summary and intended releases.
🪄 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: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3c86f278-4f2d-4925-86fb-62cb64d2648b
📒 Files selected for processing (1)
.changeset/upgrade-deps.md
- Downgrade @types/vscode to match engines.vscode floor - Bump @types/react in cli to align with react runtime - Align ui peerDependencies react floor with devDependencies Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
1 participant
Summary
Skipped (major/breaking)
inkmermaidesbuild@rslib/coreUpdated packages
@iconify-json/devicon@iconify-json/logos@iconify-json/material-icon-theme@iconify-json/simple-icons@microsoft/api-extractor@types/node@types/vscode@typescript/native-previeweslint-plugin-jsdoclaufenoxfmtoxlintturbovitest@kidd-cli/cli@kidd-cli/core@rspress/corereact@clack/promptsliquidjskatexreact-domzod-to-json-schemaTest plan