Skip to content
This repository was archived by the owner on Mar 24, 2026. It is now read-only.

chore(deps): update pnpm to v10.30.2 #43

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update pnpm to v10.30.2 #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,7 @@
"ultracite": "7.0.8",
"vitest": "^4.0.17"
},
"packageManager": "pnpm@10.28.2",
"packageManager": "pnpm@10.30.2",
"engines": {
"pnpm": "10.28.2",
"node": ">=22.18.0"
Comment on lines +141 to 144
Copy link
Copy Markdown

@sentry sentry bot Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The packageManager field specifies pnpm@10.30.2 while the engines.pnpm field requires 10.28.2, creating a version conflict within package.json.
Severity: MEDIUM

Suggested Fix

Update the engines.pnpm field in package.json to match the version specified in the packageManager field. Change "pnpm": "10.28.2" to "pnpm": "10.30.2" to ensure consistency.

Prompt for AI Agent 
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L141-L144

Potential issue: An automated dependency update modified the `packageManager` field in
`package.json` to `pnpm@10.30.2` but did not update the `engines.pnpm` field, which
remains at `10.28.2`. This creates a configuration inconsistency where different tools
may enforce conflicting versions of the package manager. For example, Corepack will use
the version from `packageManager`, while other validation scripts might enforce the
`engines` field. This can lead to unpredictable behavior, build failures in certain
environments, and increased debugging time for developers trying to resolve
environment-specific issues.

Expand Down
Loading