Skip to content

chore(deps): update dependency @types/node to v22#263

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-22.x
Closed

chore(deps): update dependency @types/node to v22#263
renovate[bot] wants to merge 1 commit intomainfrom
renovate/node-22.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Jan 8, 2026

This PR contains the following updates:

Package Change Age Confidence
@types/node (source) ^20.19.27^22.19.3 age confidence

Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate Bot requested a review from a team as a code owner January 8, 2026 02:56
@renovate renovate Bot added the 🤖 bot label Jan 8, 2026
@renovate renovate Bot requested review from cngonzalez and removed request for a team January 8, 2026 02:56
@renovate renovate Bot enabled auto-merge (squash) January 8, 2026 02:56
@claude
Copy link
Copy Markdown

claude Bot commented Jan 8, 2026

Claude finished @renovate[bot]'s task —— View job


PR Review: Node.js Types Update v20 → v22

Reviewing this dependency update for potential issues:

  • Check repository setup instructions (CLAUDE.md)
  • Analyze changed files for issues
  • Verify Node.js 22 compatibility
  • Check for breaking changes in type definitions

Review Complete - Issues Found:

1. Node.js Engine Version Constraint Conflict

The package.json specifies Node.js engine support as >=20.19.1 <22 || >=22.12 (line 62), explicitly excluding Node.js v22.0-22.11 versions. However, this PR updates to @types/node v22.19.3, which implies support for all Node.js v22 features.

Fix needed: Update engines field in package.json to align with the types version:

"engines": {
  "node": ">=20.19.1 <22 || >=22.19.0"
}

2. Large Lockfile Changes May Hide Issues

The pnpm-lock.yaml shows extensive dependency graph changes (+180/-570 lines) that could mask compatibility issues. The sanity package dependencies now reference different type signatures.

Recommendation: Run full type checking and build after merge to catch any breaking changes that may not be immediately apparent from the lockfile diff.

No other critical issues identified. The workspace catalog update correctly references the new version and lockfile changes appear to be standard dependency resolution updates.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 8, 2026

Coverage Report

Status Category Percentage Covered / Total
🔵 Lines 76.44% 5357 / 7008
🔵 Statements 75.6% 5490 / 7261
🔵 Functions 66.8% 789 / 1181
🔵 Branches 63.45% 2361 / 3721
File CoverageNo changed files found.
Generated in workflow #1365 for commit 0b6e1a7 by the Vitest Coverage Report Action

@binoy14 binoy14 closed this Jan 8, 2026
auto-merge was automatically disabled January 8, 2026 03:03

Pull request was closed

@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Jan 8, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 22.x releases. But if you manually upgrade to 22.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate Bot deleted the renovate/node-22.x branch January 8, 2026 03:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant