chore(deps): update all non-major dependencies#210
Conversation
📝 WalkthroughWalkthroughBulk version bumps across example apps and packages (Angular 21.2.12, React 19.2.6, Vite 8.0.11, pnpm 10.33.4, etc.) plus root devDependency updates and a GitHub Actions release workflow change to changesets/action v1.8.0. ChangesMonorepo dependency and workflow updates
Sequence Diagram(s)sequenceDiagram
participant Developer
participant Repo
participant CI
Developer->>Repo: Commit manifest version bumps
Repo->>CI: Trigger release workflow (changesets/action v1.8.0)
CI->>Repo: Versioning/publish per updated pins
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
View your CI Pipeline Execution ↗ for commit dc94049
☁️ Nx Cloud last updated this comment at |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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 `@package.json`:
- Line 74: The engines field in each package's package.json still requires Node
>=18 while tsdown@0.22.0 needs Node >=22.18.0; update the "engines" object in
the package.json files for the listed packages (packages/* pacer, react-pacer,
preact-pacer, solid-pacer, angular-pacer and their devtools variants) to set
"node": ">=22.18.0" (or a compatible range that includes 22.18.0) so the
declaration matches tsdown's requirement and avoids install/runtime mismatches;
ensure you change the "engines" entry inside each package.json (not other
fields) and run a quick install/test to validate.
In `@packages/pacer-devtools/package.json`:
- Line 94: Update the package's engines entry to match tsdown 0.22.0
requirements: locate the "engines" field in packages/pacer-devtools/package.json
and change the Node version from "node": ">=18" to "node": "^22.18.0 ||
>=24.0.0" so the package's declared engine compatibility aligns with the tsdown
dependency.
🪄 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: a94d9911-5fde-45f9-aa1f-aaa00b4f19f3
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (164)
.github/workflows/release.ymlexamples/angular/asyncBatch/package.jsonexamples/angular/asyncDebounce/package.jsonexamples/angular/asyncRateLimit/package.jsonexamples/angular/asyncRetry/package.jsonexamples/angular/asyncThrottle/package.jsonexamples/angular/batch/package.jsonexamples/angular/debounce/package.jsonexamples/angular/injectAsyncBatchedCallback/package.jsonexamples/angular/injectAsyncBatcher/package.jsonexamples/angular/injectAsyncDebouncedCallback/package.jsonexamples/angular/injectAsyncDebouncer/package.jsonexamples/angular/injectAsyncQueuedSignal/package.jsonexamples/angular/injectAsyncQueuer/package.jsonexamples/angular/injectAsyncRateLimiter/package.jsonexamples/angular/injectAsyncRateLimiterWithPersister/package.jsonexamples/angular/injectAsyncThrottledCallback/package.jsonexamples/angular/injectAsyncThrottler/package.jsonexamples/angular/injectBatchedCallback/package.jsonexamples/angular/injectBatcher/package.jsonexamples/angular/injectDebouncedCallback/package.jsonexamples/angular/injectDebouncedSignal/package.jsonexamples/angular/injectDebouncedValue/package.jsonexamples/angular/injectDebouncer/package.jsonexamples/angular/injectQueuedSignal/package.jsonexamples/angular/injectQueuedValue/package.jsonexamples/angular/injectQueuer/package.jsonexamples/angular/injectQueuerWithPersister/package.jsonexamples/angular/injectRateLimitedCallback/package.jsonexamples/angular/injectRateLimitedSignal/package.jsonexamples/angular/injectRateLimitedValue/package.jsonexamples/angular/injectRateLimiter/package.jsonexamples/angular/injectRateLimiterWithPersister/package.jsonexamples/angular/injectThrottledCallback/package.jsonexamples/angular/injectThrottledSignal/package.jsonexamples/angular/injectThrottledValue/package.jsonexamples/angular/injectThrottler/package.jsonexamples/angular/queue/package.jsonexamples/angular/rateLimit/package.jsonexamples/angular/throttle/package.jsonexamples/preact/asyncBatch/package.jsonexamples/preact/asyncDebounce/package.jsonexamples/preact/asyncRateLimit/package.jsonexamples/preact/asyncRetry/package.jsonexamples/preact/asyncThrottle/package.jsonexamples/preact/batch/package.jsonexamples/preact/debounce/package.jsonexamples/preact/queue/package.jsonexamples/preact/rateLimit/package.jsonexamples/preact/throttle/package.jsonexamples/preact/useAsyncBatchedCallback/package.jsonexamples/preact/useAsyncBatcher/package.jsonexamples/preact/useAsyncDebouncedCallback/package.jsonexamples/preact/useAsyncDebouncer/package.jsonexamples/preact/useAsyncQueuedState/package.jsonexamples/preact/useAsyncQueuer/package.jsonexamples/preact/useAsyncRateLimiter/package.jsonexamples/preact/useAsyncRateLimiterWithPersister/package.jsonexamples/preact/useAsyncThrottledCallback/package.jsonexamples/preact/useAsyncThrottler/package.jsonexamples/preact/useBatchedCallback/package.jsonexamples/preact/useBatcher/package.jsonexamples/preact/useDebouncedCallback/package.jsonexamples/preact/useDebouncedState/package.jsonexamples/preact/useDebouncedValue/package.jsonexamples/preact/useDebouncer/package.jsonexamples/preact/useQueuedState/package.jsonexamples/preact/useQueuedValue/package.jsonexamples/preact/useQueuer/package.jsonexamples/preact/useQueuerWithPersister/package.jsonexamples/preact/useRateLimitedCallback/package.jsonexamples/preact/useRateLimitedState/package.jsonexamples/preact/useRateLimitedValue/package.jsonexamples/preact/useRateLimiter/package.jsonexamples/preact/useRateLimiterWithPersister/package.jsonexamples/preact/useThrottledCallback/package.jsonexamples/preact/useThrottledState/package.jsonexamples/preact/useThrottledValue/package.jsonexamples/preact/useThrottler/package.jsonexamples/preact/util-comparison/package.jsonexamples/react/asyncBatch/package.jsonexamples/react/asyncDebounce/package.jsonexamples/react/asyncRateLimit/package.jsonexamples/react/asyncRetry/package.jsonexamples/react/asyncThrottle/package.jsonexamples/react/batch/package.jsonexamples/react/debounce/package.jsonexamples/react/queue/package.jsonexamples/react/rateLimit/package.jsonexamples/react/react-query-debounced-prefetch/package.jsonexamples/react/react-query-queued-prefetch/package.jsonexamples/react/react-query-throttled-prefetch/package.jsonexamples/react/throttle/package.jsonexamples/react/useAsyncBatchedCallback/package.jsonexamples/react/useAsyncBatcher/package.jsonexamples/react/useAsyncDebouncedCallback/package.jsonexamples/react/useAsyncDebouncer/package.jsonexamples/react/useAsyncQueuedState/package.jsonexamples/react/useAsyncQueuer/package.jsonexamples/react/useAsyncRateLimiter/package.jsonexamples/react/useAsyncRateLimiterWithPersister/package.jsonexamples/react/useAsyncThrottledCallback/package.jsonexamples/react/useAsyncThrottler/package.jsonexamples/react/useBatchedCallback/package.jsonexamples/react/useBatcher/package.jsonexamples/react/useDebouncedCallback/package.jsonexamples/react/useDebouncedState/package.jsonexamples/react/useDebouncedValue/package.jsonexamples/react/useDebouncer/package.jsonexamples/react/useQueuedState/package.jsonexamples/react/useQueuedValue/package.jsonexamples/react/useQueuer/package.jsonexamples/react/useQueuerWithPersister/package.jsonexamples/react/useRateLimitedCallback/package.jsonexamples/react/useRateLimitedState/package.jsonexamples/react/useRateLimitedValue/package.jsonexamples/react/useRateLimiter/package.jsonexamples/react/useRateLimiterWithPersister/package.jsonexamples/react/useThrottledCallback/package.jsonexamples/react/useThrottledState/package.jsonexamples/react/useThrottledValue/package.jsonexamples/react/useThrottler/package.jsonexamples/react/util-comparison/package.jsonexamples/solid/asyncBatch/package.jsonexamples/solid/asyncDebounce/package.jsonexamples/solid/asyncRateLimit/package.jsonexamples/solid/asyncThrottle/package.jsonexamples/solid/batch/package.jsonexamples/solid/createAsyncBatcher/package.jsonexamples/solid/createAsyncDebouncer/package.jsonexamples/solid/createAsyncQueuer/package.jsonexamples/solid/createAsyncRateLimiter/package.jsonexamples/solid/createAsyncThrottler/package.jsonexamples/solid/createBatcher/package.jsonexamples/solid/createDebouncedSignal/package.jsonexamples/solid/createDebouncedValue/package.jsonexamples/solid/createDebouncer/package.jsonexamples/solid/createQueuedSignal/package.jsonexamples/solid/createQueuer/package.jsonexamples/solid/createRateLimitedSignal/package.jsonexamples/solid/createRateLimitedValue/package.jsonexamples/solid/createRateLimiter/package.jsonexamples/solid/createThrottledSignal/package.jsonexamples/solid/createThrottledValue/package.jsonexamples/solid/createThrottler/package.jsonexamples/solid/debounce/package.jsonexamples/solid/queue/package.jsonexamples/solid/rateLimit/package.jsonexamples/solid/throttle/package.jsonexamples/vanilla/LiteBatcher/package.jsonexamples/vanilla/LiteDebouncer/package.jsonexamples/vanilla/LiteQueuer/package.jsonexamples/vanilla/LiteRateLimiter/package.jsonexamples/vanilla/LiteThrottler/package.jsonexamples/vanilla/liteBatch/package.jsonexamples/vanilla/liteDebounce/package.jsonexamples/vanilla/liteQueue/package.jsonexamples/vanilla/liteRateLimit/package.jsonexamples/vanilla/liteThrottle/package.jsonpackage.jsonpackages/angular-pacer/package.jsonpackages/pacer-devtools/package.jsonpackages/preact-pacer/package.jsonpackages/react-pacer/package.json
| "size-limit": "^12.1.0", | ||
| "tinyglobby": "^0.2.16", | ||
| "tsdown": "^0.21.10", | ||
| "tsdown": "^0.22.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Check Node.js version requirements in package.json and CI config
# Check for engines field in all package.json files
echo "=== Checking package.json engines fields ==="
fd -e json package.json -x jq -r 'select(.engines.node != null) | "File: " + input_filename + " | Node: " + .engines.node'
# Check CI workflows for Node.js version matrix
echo -e "\n=== Checking GitHub Actions Node.js versions ==="
rg -n "node-version" .github/workflows/ -A 2 -B 1
# Check .nvmrc or .node-version files
echo -e "\n=== Checking .nvmrc or .node-version ==="
fd -t f "^\.nvmrc$|^\.node-version$" -x cat {}Repository: TanStack/pacer
Length of output: 772
🌐 Web query:
tsdown 0.22.0 Node.js version requirement
💡 Result:
tsdown v0.22.0 requires Node.js 22.18.0 or later (engines: node >=22.18.0). [1][2][3] Evidence: - The v0.22.0 release notes state: “Upgrade to Node.js 22.18.0 or later.” [1] - The tsdown website getting-started guide repeats the requirement: “tsdown requires Node.js version 22.18.0 or higher.” [3] - The v0.22.0 release/breaking-change entry notes “Drop Node.js < 22.18.0 support” and shows the engines change to >=22.18.0. [4][1] Related (config-loader note for Node users): if you’re on Node without native TypeScript support and rely on the default auto loader, you may need to install unrun (or use the tsx loader). [1][5]
Citations:
- 1: https://github.com/rolldown/tsdown/releases/tag/v0.22.0
- 2: https://newreleases.io/project/npm/tsdown/release/0.22.0
- 3: https://tsdown.dev/guide/getting-started
- 4: rolldown/tsdown@a104223
- 5: https://github.com/rolldown/tsdown/releases
Update Node.js version requirement to >=22.18.0 across the monorepo.
tsdown 0.22.0 requires Node.js >=22.18.0, but the repository's engines field in all package.json files is set to >=18. Update the Node.js version constraint in the following packages:
- packages/pacer/package.json
- packages/pacer-lite/package.json
- packages/react-pacer/package.json
- packages/react-pacer-devtools/package.json
- packages/preact-pacer/package.json
- packages/preact-pacer-devtools/package.json
- packages/solid-pacer/package.json
- packages/solid-pacer-devtools/package.json
- packages/pacer-devtools/package.json
- packages/angular-pacer/package.json
🤖 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 `@package.json` at line 74, The engines field in each package's package.json
still requires Node >=18 while tsdown@0.22.0 needs Node >=22.18.0; update the
"engines" object in the package.json files for the listed packages (packages/*
pacer, react-pacer, preact-pacer, solid-pacer, angular-pacer and their devtools
variants) to set "node": ">=22.18.0" (or a compatible range that includes
22.18.0) so the declaration matches tsdown's requirement and avoids
install/runtime mismatches; ensure you change the "engines" entry inside each
package.json (not other fields) and run a quick install/test to validate.
| "devDependencies": { | ||
| "rolldown-plugin-solid": "^0.2.1", | ||
| "tsdown": "^0.21.10", | ||
| "tsdown": "^0.22.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify tsdown 0.22.0 requirements and breaking changes
# Check tsdown package.json for engine requirements
curl -s https://registry.npmjs.org/tsdown/0.22.0 | jq '.engines'
# Check for any usage of 'unrun' in the package that might break
rg -n 'unrun' --type-add 'config:*.{json,js,ts,mjs,cjs}' --type config
# Inspect tsconfig to see if dts settings exist
fd -e json 'tsconfig' --exec cat {}Repository: TanStack/pacer
Length of output: 50371
🏁 Script executed:
sed -n '70,80p' packages/pacer-devtools/package.jsonRepository: TanStack/pacer
Length of output: 225
Update engines field to match tsdown 0.22.0 requirements.
tsdown 0.22.0 requires Node.js ^22.18.0 || >=24.0.0, but this package specifies "node": ">=18". This creates a compatibility conflict—users on Node.js 18, 19, 20, 21, or 22.0-22.17.x will be unable to use tsdown 0.22.0.
Update the engines field in packages/pacer-devtools/package.json to: "node": "^22.18.0 || >=24.0.0"
🤖 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 `@packages/pacer-devtools/package.json` at line 94, Update the package's
engines entry to match tsdown 0.22.0 requirements: locate the "engines" field in
packages/pacer-devtools/package.json and change the Node version from "node":
">=18" to "node": "^22.18.0 || >=24.0.0" so the package's declared engine
compatibility aligns with the tsdown dependency.
This PR contains the following updates:
^21.2.9→^21.2.10^21.2.9→^21.2.10^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^21.2.11→^21.2.12^0.13.0→^0.13.1v1.7.0→v1.8.0^6.11.0→^6.12.210.33.2→10.33.4^0.3.18→^0.3.20^19.2.5→^19.2.6^19.2.5→^19.2.6^19.2.5→^19.2.6^0.21.10→^0.22.0^8.0.10→^8.0.11Release Notes
angular/angular-cli (@angular/build)
v21.2.10Compare Source
@angular/cli
angular/angular (@angular/common)
v21.2.12Compare Source
core
forms
TanStack/store (@tanstack/preact-store)
v0.13.1Compare Source
Patch Changes
changesets/action (changesets/action)
v1.8.0Compare Source
Minor Changes
f5dbf72Thanks @tom-sherman! - Support draft version PR modes with a newprDraftinput. Usecreateto create new version PRs as drafts, oralwaysto also convert existing version PRs back to draft when updating them.Patch Changes
#502
6002dbdThanks @oshytiko! - Fixed initial.changesetstate being picked up, whencwdparameter is provided#536
81b3f61Thanks @radnan! - Fixed.changesetstate being picked for the version command whencwdparameter is providedwebpro-nl/knip (knip)
v6.12.2: Release 6.12.2Compare Source
d54074d) - thanks @cyphercodes!.ts/.ctsconfig (close #1732) (f37c5da)616739d)081dfc8)5dd0b8a)v6.12.1: Release 6.12.1Compare Source
de33a2c) - thanks @lishaduck!0fe8dc3) - thanks @re-taro!370236d) - thanks @jakeleventhal!4dcd756) - thanks @jakeleventhal!2d555a1) - thanks @jeffrey-takuma!c3dcc8f)78fd581)7e689bf)v6.12.0: Release 6.12.0Compare Source
2354194)4afc873)b106065)c226a72)ddcf7de) - thanks @jakeleventhal!3a2c22b)3a2c22b(8300078)d56ee51)7195b0a)60f8482) - thanks @jakeleventhal!>inside SFC<script>attribute values (resolve #1714) (9e5501f)7cc4fc1)10f97c1) - thanks @jakeleventhal!53236b5)727f842)0db3300)isTreatConfigHintsAsErrors(f27c3f4)aab1e83)c709a5a)pnpm/pnpm (pnpm)
v10.33.4: pnpm 10.33.4Compare Source
Patch Changes
Pin the integrity of git-hosted tarballs (codeload.github.com, gitlab.com, bitbucket.org) in the lockfile so that subsequent installs detect a tampered or substituted tarball and refuse to install it. Previously the lockfile only stored the tarball URL for git dependencies, so a compromised git host or a man-in-the-middle could serve arbitrary code on later installs without lockfile changes.
A new
gitHosted: truefield is recorded on git-hosted tarball resolutions in the lockfile, letting every reader/writer route them by a single typed check instead of pattern-matching the tarball URL in each call site. Lockfiles written by older pnpm versions are enriched on load (URL fallback) so the field can be relied on uniformly across the codebase.Fix a regression where
pnpm --recursive --filter '!<pkg>' run/exec/test/addwould include the workspace root in the matched projects. The workspace root is now correctly excluded by default when only negative--filterarguments are provided, matching the documented behavior. To include the root, pass--include-workspace-root#11341.Platinum Sponsors
Gold Sponsors
v10.33.3Compare Source
publint/publint (publint)
v0.3.20Compare Source
Patch Changes
Suggest adding
engines.nodewhen it is missing from detected Node.js packages (#226)Loosen "breaking change" wording in lint messages (
7bb3f4f)v0.3.19Compare Source
Patch Changes
Add
NESTED_PACKAGE_JSON_FIELD_IGNOREDto warn when published nestedpackage.jsonfiles define"exports"or"imports", which Node.js ignores outside the package root. (#224)Fix internal browser directory traversal logic (#224)
facebook/react (react)
v19.2.6: 19.2.6 (May 6th, 2026)Compare Source
React Server Components
(by @eps1lon and @unstubbable)
rolldown/tsdown (tsdown)
v0.22.0Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
🔄 Migration Guide
Node.js version
Upgrade to Node.js 22.18.0 or later. Bun and Deno remain supported (experimental).
unrunis no longer bundledIf your environment relies on the
unrunconfig loader (i.e. you're on a Node version without native TypeScript support and use the defaultautoloader), install it manually:npm i -D unrun # or, alternatively, the new tsx loader: npm i -D tsxIf you use Node.js 22.18.0+ with native TypeScript support, no change is needed — the
autoloader will picknative.dtsauto-enabled from tsconfigIf your
tsconfig.jsonhascompilerOptions.declaration: truebut you do not want tsdown to emit.d.tsfiles, opt out explicitly:exports.binauto-detectionAny entry chunk containing a shebang (e.g.
#!/usr/bin/env node) now causes tsdown to write abinfield inpackage.jsonautomatically. The semantics differ slightly from explicitbin: true:truefalseTo opt out entirely:
Links
vitejs/vite (vite)
v8.0.11Compare Source
Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
Tests
Configuration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.