fix(deps): update all non-major dependencies - #1707
Conversation
|
35c33bd to
d80f591
Compare
dawsontoth
left a comment
dawsontoth
left a comment
There was a problem hiding this comment.
Blocking on one package in this batch: @tanstack/react-router 1.170.32 → 1.170.33 breaks tsc -b. Everything else in the batch is clean. Reproduced and isolated locally (macOS, Node 24.21.0, pnpm 12.4.1).
The failure
This is what reddens Verify PR — the job fails at Type-check, which then skips Run unit tests, Run lint and Build. The Report coverage error further down (ENOENT: coverage-summary.json) is just fallout from vitest never running; it is not a second problem.
src/router/useNewRouter.ts(25,4): error TS2322:
Type '({ className, error, title, showReturnToHome, children }: ErrorProps) => Element'
is not assignable to type 'ErrorRouteComponent | undefined'.
Type ... is not assignable to type
'LazyExoticComponent<(props: ErrorComponentProps) => any> & { preload?: ... }'.
... is missing the following properties from type
'LazyExoticComponent<(props: ErrorComponentProps) => any>': _result, $$typeof
The offending line is defaultErrorComponent: ErrorComponent in createRouter(...). Upstream narrowed ErrorRouteComponent so it now only accepts a LazyExoticComponent, not a plain function component. Ours is a plain function component (src/components/ErrorComponent.tsx), and defaultNotFoundComponent right above it is the same shape.
Isolated to @tanstack/react-router, and bisected to the patch
Holding only @tanstack/react-router back on this branch, with every other bump in the batch left in place:
@tanstack/react-router |
tsc -b |
|---|---|
| 1.170.32 (base) | exit 0 |
| 1.170.33 | exit 1 |
| 1.170.34 | exit 1 |
| 1.170.35 (this PR) | exit 1 |
So 1.170.33 introduced it, and stage type-checks clean today (verified — tsc -b exit 0 on 6320a01ef).
A type-narrowing of a public prop in a patch release is an upstream regression, not something we should absorb quietly. Wrapping ErrorComponent in React.lazy to satisfy it would be a real code change made to appease a probable bug, and it would regress the error boundary to a suspense boundary.
Ask
Please split @tanstack/react-router out of this batch — hold it at 1.170.32 (it is already pinned exactly, so a Renovate ignore/pin entry) and let the rest land. I'd rather not hold three good bumps behind one upstream types regression. Worth an upstream issue against TanStack Router too.
The rest of the batch is fine
zod 4.5.4 → 4.6.2, harper 5.2.9 → 5.2.10 and packageManager pnpm 12.3.4 → 12.4.1 are all clean — with @tanstack/react-router held at 1.170.32 and every other bump from this PR in place, tsc -b exits 0.
Not caused by this PR
renovate/artifacts is red, as it is on every studio update that touches the e2e workspace — the pnpm --no-save artifact step, not the lockfile. The lockfile here is fine (pnpm install --frozen-lockfile exit 0). Don't chase it.
8f7ab18 to
f6e2104
Compare
Re-checked on the new head
|
@tanstack/react-router |
tsc -b |
|---|---|
| 1.170.32 | ✅ clean |
| 1.170.33 | ❌ TS2322 |
| 1.170.34 | ❌ TS2322 |
| 1.170.35 (this PR) | ❌ TS2322 — matches CI |
| 1.170.36 (latest, published 09-13) | ❌ TS2322 |
ErrorBoundaryTypes being exported for augmentation, with that doc comment, is upstream saying the unknown default is intentional and permanent.
This is also hiding a real bug of ours
ErrorComponent renders {error.message} with no guard. The route boundary genuinely can hand us a non-Error — a thrown string, or a rejected promise carrying anything — and today that silently renders nothing. The type change is upstream telling us the truth; our type was the optimistic one.
Suggested fix — verified green
interface ErrorProps {
className?: string | undefined;
- error: Error | { message: string | ReactNode };
+ // The router's error boundary hands us whatever was thrown, which is not
+ // necessarily an Error. @tanstack/react-router >= 1.170.33 types this as
+ // `unknown`, so accept anything and narrow before reading `.message`.
+ error: unknown;
title?: string;
showReturnToHome?: boolean;
children?: ReactNode;
}
+function errorMessage(error: unknown): ReactNode {
+ if (typeof error === 'object' && error !== null && 'message' in error) {
+ return (error as { message: string | ReactNode }).message;
+ }
+ return typeof error === 'string' ? error : 'An unexpected error occurred.';
+}
+
export function ErrorComponent({ className, error, title, showReturnToHome, children }: ErrorProps) {
@@
- <CardDescription>{error.message}</CardDescription>
+ <CardDescription>{errorMessage(error)}</CardDescription>error: unknown still accepts the five direct <ErrorComponent error={{ message: ... }} /> call sites in clusters/upsert/index.tsx, clusters/upsert/ClusterRegions.tsx and instance/apis/APIDocs.tsx — they keep working untouched.
With that patch applied on this head at 1.170.35:
tsc -b --force exit 0
vitest run 345 files — 3128 passed, 11 skipped, 0 failed
oxlint . exit 0, clean
vite build ✓ built in 2.69s
If you'd rather not touch the component in a dependency PR, the one-line alternative is to augment the interface upstream provides for exactly this:
declare module '@tanstack/router-core' {
interface ErrorBoundaryTypes {
error: Error | { message: string | ReactNode };
}
}I'd take the first one — it fixes the latent unguarded .message rather than asserting the old assumption back into place.
The other red check is not real
renovate/artifacts ("Artifact file update failure") is the recurring lockfile-artifact flake on this repo, not a lockfile problem. pnpm install --frozen-lockfile resolves cleanly here (exit 0), so the committed pnpm-lock.yaml is in sync. The Report coverage error inside Verify PR is likewise just fallout from vitest never running after the type-check failed.
Happy to push the fix onto this branch if you'd like — say the word.
f6e2104 to
e372acc
Compare
Re-checked on the new head
|
previous head f6e21049 |
this head e372accd |
|
|---|---|---|
react / react-dom |
19.2.8 | 19.3.0 |
@types/react / @types/react-dom |
19.2.18 / 19.2.7 | 19.3.0 / 19.3.0 |
zod |
4.6.2 | 4.6.4 |
vite |
8.2.2 | 8.3.0 |
oxlint |
1.81.0 | 1.82.0 |
react-hook-form |
7.87.0 | 7.88.0 |
react is ^19.0.0 in package.json, so 19.3.0 arrives through the lockfile rather than through a visible manifest line. Worth calling out because CI cannot tell you anything about it — Verify PR dies at Type-check and then skips Run unit tests, Run lint and Build (confirmed on this exact run: 35044192636). So a React minor, a Vite minor and a zod bump are currently landing with zero functional signal behind a single type error.
The blocker is unchanged
Reproduced on e372accd as-is (macOS, Node 24.21.0, pnpm 12.4.1, pnpm install --frozen-lockfile exit 0):
src/router/useNewRouter.ts(25,4): error TS2322:
Type '({ className, error, title, showReturnToHome, children }: ErrorProps) => Element'
is not assignable to type 'ErrorRouteComponent | undefined'.
Same @tanstack/react-router 1.170.35 / router-core ErrorComponentProps<TError = ErrorBoundaryTypes['error']> → unknown cause I laid out last time. Still not an upstream regression, still not fixable by waiting, still not something to paper over with React.lazy.
The rest of the enlarged batch is verified clean
I applied only the one-file fix — widening ErrorProps.error to unknown in src/components/ErrorComponent.tsx and narrowing before reading .message — and changed nothing else on this head:
tsc -b --force exit 0
pnpm test 345 files — 3128 passed | 11 skipped (3139)
pnpm lint exit 0 (oxlint 1.82.0, clean)
pnpm build exit 0 (vite 8.3.0)
So React 19.3.0, @types/react 19.3.0, vite 8.3.0, zod 4.6.4, oxlint 1.82.0, harper 5.2.10 and pnpm 12.4.1 are all fine. The router type error is still the sole thing standing between this PR and green, and it is one file.
Ask (unchanged, and now worth more)
Fix ErrorComponent's prop type rather than pinning the router. It's a few lines, it unblocks a batch that now includes a React minor, and it fixes a real latent bug on the way: {error.message} is rendered unguarded today, so a thrown string or non-Error renders nothing in the error boundary. Once that lands, this whole PR goes green as-is — no pin, no ignore rule, no split.
I'm happy to push that commit onto this branch if it's easier — say the word. (Renovate will stop auto-updating the PR body once a human pushes, which is fine at this point.)
Not caused by this PR
renovate/artifacts is red again — ERR_PNPM_STRICT_MIN_RELEASE_AGE_REQUIRES_SAVE on e2e/pnpm-lock.yaml, the pnpm --no-save artifact step. It fires on every studio update touching the e2e workspace. The lockfile itself is fine (--frozen-lockfile exit 0). Don't chase it.
2ace1a8 to
547c7f9
Compare
Re-checked on the new head
|
| value | |
|---|---|
e2e/package.json → packageManager |
pnpm@12.4.1 |
e2e/pnpm-lock.yaml → packageManagerDependencies.pnpm |
12.3.4 |
And e2e/Dockerfile:14 is RUN pnpm install --frozen-lockfile, so building the harness image fails outright:
$ cd e2e && pnpm install --frozen-lockfile
Error: ERR_PNPM_FROZEN_LOCKFILE_WITH_OUTDATED_LOCKFILE
× resolve package manager dependencies
╰─▶ Cannot update packageManagerDependencies with "frozen-lockfile" because
the lockfile is not up to date
This is caused by this PR — on the base ab1eb190 both sides read 12.3.4 and the frozen install is clean. No PR check catches it, because the e2e harness is driven by the out-of-repo trusted-lane scheduler rather than by a workflow in this repo. That's precisely why it needs saying here: it would land green and break the e2e lane later.
The fix is mechanical — regenerate the one lockfile:
cd e2e && pnpm install --ignore-scriptsI ran it. The delta is packageManagerDependencies 12.3.4 → 12.4.1 plus the corresponding @pnpm/exe.* platform entries, and nothing else — no test dependency moves (@playwright/test 1.62.1, mailosaur 11.1.1, typescript 7.0.2, dotenv 17.4.2, @types/node 24.13.3 all unchanged). After that, pnpm install --frozen-lockfile in e2e/ is clean:
✓ Lockfile passes supply-chain policies (verified 8d ago)
Lockfile is up to date, resolution step is skipped
So the general shape of my earlier advice still holds — renovate/artifacts red on this repo is usually cosmetic — but "usually" isn't "always", and the tell is whether the batch actually changed something under e2e/. This one did.
The blocker is unchanged (router is now 1.170.36)
Reproduced on 547c7f93 as-is (macOS, Node 24.21.0, pnpm 12.4.1, root pnpm install --frozen-lockfile exit 0):
src/router/useNewRouter.ts(25,4): error TS2322:
Type '({ className, error, title, showReturnToHome, children }: ErrorProps) => Element'
is not assignable to type 'ErrorRouteComponent | undefined'.
Same cause as .33 and .35: router-core types the boundary error as unknown, ErrorComponent declares error: Error | { message: string | ReactNode }, and the parameter position is contravariant. Note the error text dangles LazyExoticComponent at you — that's just TS reporting the last union member, not a hint to reach for React.lazy. Still not an upstream regression, still not fixable by waiting, still one file.
The rest of the batch is verified clean
Applied only the one-file fix (widen ErrorProps.error to unknown, narrow before reading .message), nothing else touched:
tsc -b --force exit 0
pnpm test 346 files — 3144 passed | 11 skipped (3155)
pnpm lint exit 0 (oxlint, clean)
pnpm format exit 0 (dprint, clean)
vite build ✓ built in 3.00s
And isolated the blocker from the other direction — original ErrorComponent, only @tanstack/react-router reverted to 1.170.32:
tsc -b --force exit 0
So zod 4.6.5, harper 5.2.10, @tanstack/react-router-devtools 1.167.2, Node 24.21.0 and pnpm 12.4.1 are all fine. Two things stand between this PR and green, and both are small.
Ask
- Fix
ErrorComponent's prop type rather than pinning the router — it also fixes a live latent bug, since{error.message}is rendered unguarded today and a thrown string renders nothing in the boundary. - Regenerate
e2e/pnpm-lock.yaml(one command above).
Happy to push both onto this branch — say the word.
Nits, pre-existing, not blocking
e2e/Dockerfile has two bits of drift Renovate isn't tracking and this PR widens:
- line 7 pins
corepack prepare pnpm@11.20.0 --activatewhilee2e/package.jsonnow asks for12.4.1— corepack honours thepackageManagerfield anyway, so the pin is inert and misleading rather than harmful. - the header comment says Node is pinned to
.nvmrc (24.19.0);.nvmrcwas24.20.0before this PR and is24.21.0after. TheFROMline updates correctly, only the prose is stale.
547c7f9 to
b598fad
Compare
Re-checked on the new head
|
…e change
Two things in this batch needed work before it could go green. This commit
takes the four updates that are safe as-is and defers the one that isn't.
**Deferred: the TanStack router pair.** `@tanstack/react-router`
1.170.32 -> 1.170.36 breaks `tsc -b`:
src/router/useNewRouter.ts(25,4): error TS2322:
Type '({ className, error, ... }: ErrorProps) => Element'
is not assignable to type 'ErrorRouteComponent | undefined'.
`router-core` now types the boundary error as `unknown`, our
`ErrorComponent` declares `error: Error | { message: string | ReactNode }`,
and the parameter position is contravariant. That is an intentional
upstream change, not a regression, so the fix belongs in our
`ErrorProps` -- which makes it a source change, not a dependency bump,
and it wants its own review. Reverted to 1.170.32 here.
`@tanstack/react-router-devtools` 1.167.2 reverts with it, not as
collateral: its peer range is `@tanstack/react-router: ^1.170.36`, so
keeping the devtools bump against a 1.170.32 router would be an unmet
peer. 1.167.1 wants `^1.170.19`, which 1.170.32 satisfies. `pnpm peers
check` reports exactly one unmet peer on this head (`@aws-sdk/client-s3`,
pre-existing and unrelated) -- identical to the batch before this commit.
**Fixed: the e2e lockfile.** The batch bumps `e2e/package.json`'s
`packageManager` to `pnpm@12.4.1`. pnpm 12 records that in the lockfile
as `packageManagerDependencies`, and the Renovate artifact step that
would have refreshed it died on
`ERR_PNPM_STRICT_MIN_RELEASE_AGE_REQUIRES_SAVE`, so the two disagreed and
`e2e/Dockerfile`'s `pnpm install --frozen-lockfile` failed outright. No
check in this repo covers it -- the e2e harness runs from the
out-of-repo trusted-lane scheduler -- so it would have landed green and
broken the e2e lane later. Regenerated; the delta is
`packageManagerDependencies` and the `@pnpm/exe.*` platform entries and
nothing else. No test dependency moves.
What this batch still carries: Node 24.20.0 -> 24.21.0 (`.nvmrc` and the
e2e Dockerfile base), pnpm 12.3.4 -> 12.4.1 in both manifests,
`zod` 4.5.4 -> 4.6.5, and `harper` 5.2.9 -> 5.2.12 (dev).
Verified on this head, with no source files touched:
pnpm install --frozen-lockfile exit 0 (root and e2e)
tsc -b --force exit 0
pnpm test 346 files - 3144 passed | 11 skipped
pnpm lint exit 0 (oxlint)
pnpm format exit 0 (dprint)
pnpm build exit 0 (built in 2.84s)
Note that Renovate will re-propose the router pair on its next run; the
durable fix is to widen `ErrorProps.error` to `unknown` and narrow before
reading `.message`, which also closes a live latent bug -- `{error.message}`
renders nothing today when a string is thrown.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
Coverage Report
File CoverageNo changed files found. |
Both blockers are resolved in eb69f15 — the router pair is deferred out of the batch and the e2e lockfile is regenerated. Verify PR and Verify Commits are green. Dismissing my own stale review; this still needs a human approval.
|
Took this over and pushed What's still in
What came out, and why the devtools came with it
So keeping 1.167.2 against a 1.170.32 router would have left an unmet peer. This also corrects something in my earlier comment: I'd written that the devtools bump was "verified clean" from my isolation test, where I reverted only the router. That test did typecheck — but it was sitting on an unmet peer I didn't check for at the time. Reverting the pair together is the correct move, and The e2e lockfile is fixed, not deferredRegenerated Verification — no source files touched
One thing to decide, not urgentRenovate will re-propose the router pair on its next run — nothing here holds it back, and The durable fix is still the one-file change: widen |
1 participant
This PR contains the following updates:
4.0.96→4.0.1034.0.108(+4)7.12.0→7.13.07.12.0→7.13.05.23.0→5.24.11.12.7→1.12.101.62.1→1.63.06.9.0→6.10.09.15.0→9.16.01.170.32→1.170.361.170.38(+1)1.167.1→1.167.224.13.3→24.13.424.13.524.13.3→24.13.424.13.519.2.18→19.3.019.2.7→19.3.07.0.93→7.0.1007.0.105(+4)1.12.2→1.12.620.14.0→20.14.55.2.9→5.2.125.2.131.41.0→1.46.01.47.013.2.0→13.3.013.4.024.20.0→24.21.024.20.0-bookworm→24.21.0-bookworm1.81.0→1.83.012.3.4→12.4.112.4.219.2.8→19.3.019.2.8→19.3.020.1.1→20.1.27.87.0→7.88.03.6.0→3.7.08.2.2→8.3.02.9.0→2.9.14.5.4→4.6.5Release Notes
vercel/ai (@ai-sdk/react)
v4.0.103Compare Source
Patch Changes
6431635]v4.0.102Compare Source
Patch Changes
615ac89]v4.0.101Compare Source
Patch Changes
9d8e5a1: fix(react): abort chats when theiruseChatid changes during a stream5ec21a6]db59d78]7469a3b]f87bf07]bc5cb7a]a5f449a]813bb36]c43e4b7]v4.0.100Compare Source
Patch Changes
ef3bac4]9942196]v4.0.99Compare Source
Patch Changes
912fb01]c595e6e]v4.0.98Compare Source
Patch Changes
27f6d7a]v4.0.97Compare Source
Patch Changes
a4ba394]36b3364]45099da]9e1d1b2]a495511]DataDog/browser-sdk (@datadog/browser-rum)
v7.13.0Compare Source
Public Changes:
Internal Changes:
DataDog/datadog-ci (@datadog/datadog-ci)
v5.24.1Compare Source
What's Changed
Dependencies
Serverless
Full Changelog: DataDog/datadog-ci@v5.24.0...v5.24.1
v5.24.0Compare Source
What's Changed
datadog-ci
Dependencies
RUM
Serverless
Synthetics
ip-addressto10.5.0by @Drarig29 in #2450Chores
New Contributors
Full Changelog: DataDog/datadog-ci@v5.23.0...v5.24.0
HarperFast/skills (@harperfast/skills)
v1.12.10Compare Source
Bug Fixes
v1.12.9Compare Source
Bug Fixes
v1.12.8Compare Source
Bug Fixes
microsoft/playwright (@playwright/test)
v1.63.0Compare Source
stripe/react-stripe-js (@stripe/react-stripe-js)
v6.10.0Compare Source
New features
Fixes
Changed
stripe/stripe-js (@stripe/stripe-js)
v9.16.0Compare Source
New features
Fixes
Changed
TanStack/router (@tanstack/react-router)
v1.170.36Compare Source
Patch Changes
#8390
b747fb8- Keep the Link location cache out of server bundles:buildLocationonly creates, reads and writes it whenisServeris false. Render React Links on the server without the extra prop copies and the forwarded-ref hook. Link SSR rendering is 20-40% faster in the Link benchmarks and the React Start SSR request loop about 7% faster.React
activePropsandinactivePropsnow follow one precedence rule on every link, including links whose destination is blocked for using a disallowed scheme: state props override element props,refand event handlers, whilehref,disabledandtargetstay controlled by the router. Previously a blocked link ignored arefor handler from its inactive props.React
LinkanduseLinkPropssplit router options from element props with one key set on the client and the server. Element props pass through as given: external links forward them verbatim, falsy values included, anduseLinkPropsnow returnschildrenfor router-controlled links as it already did for external ones.#8324
6387d58- Reuse hydration snapshot getters to avoid unnecessary store-instance effect updates when Links and other hydration-aware components rerender.#8318
9b2adaf- Allow active and inactive Link props to override base element props in React and Solid while preserving class/style merging. Keep React'shref,target, anddisabledvalues controlled by routing options. Preserve Vue object and nested-array class bindings, including reactive updates and server rendering, without mutating cached bindings during VNode normalization.#8327
634da91- MakepathParamsAllowedCharactersinitialization-only. Configure it when creating the router; changing allowed characters requires a new router instance. Remove decoder-update bookkeeping and decoder-change checks from route-owned path caches.#8370
e9396c9- Stop exporting the internalisPlainObjectandisPlainArrayhelpers.#8324
6387d58- Avoid a redundant prop copy when rendering native Links while preserving custom-component props and the public hook result.#8252
7e349c3- Reduce the bundle cost of shared Link pathname interpolation while preserving its rendering performance. Reuse one interpolation pass for pathname and optional metadata, keep the bounded cache on the router, and simplify React Link active-state and prop merging.#8370
e9396c9- Reuse built locations for Links whose destination does not depend on the current location.buildLocationkeeps the result per options object when the build never read the current location, and the ReactLinkpasses one stable options object per instance, so navigations resolve unchanged Links with a lookup instead of a full build. The per-route pathname interpolation cache this replaces is removed. Linkparams,searchandactiveOptionsare compared by value on render, so inline object literals with unchanged contents keep reusing the Link's location. Pass a new object to change a destination; like any other React prop, an object mutated in place is not re-read.Updated dependencies [
d76a332,b747fb8,6cfb1e8,700a714,700a714,8fff7fa,f021f6d,ae68535,7e349c3,873c830,7e349c3,634da91,e9396c9,634da91,f151ab0,bc57fa3,9872d2a,d76a332,634da91,634da91,7e349c3,9448caa,e9396c9,700a714,634da91,634da91]:v1.170.35Compare Source
Patch Changes
8c43c71- Upgrade TanStack Store to 0.11 and migrate router subscriptions to useSelector, preserving selector comparisons and Vue subscription cleanup.v1.170.34Compare Source
Patch Changes
#8279
aee42c6- Avoid allocating event-handler arrays and wrapper functions for links without user-supplied event handlers.#8308
9c1871c- Validate navigation and redirect destinations, keep ambiguous relative URLs on the current origin, and constrain prerender requests and output paths. Prevent redirect headers from appearing in serialized server function response bodies.Preserve native form HTTP redirects, route error handling and masks for document redirects, and per-navigation destinations for shared loader redirects. Avoid redundant origin parsing and reduce link styling and server-rendering work. Configured origins must already be normalized.
Keep blocked-link inactive props consistent during React hydration, honor explicit redirect Location headers before checking route options, and refresh Vue link state when destinations become internal. Reuse the protocol-relative URL check while parsing redirect schemes once.
Reduce React link bundle size by sharing pathname comparisons, state-prop selection, and element creation.
Share normalized pathname comparisons in Solid and Vue links to reduce bundle size.
#8311
9aec5a7- React Links resolve state props without temporary class-name arrays or unnecessary style copies.Updated dependencies [
f9836f1,9c1871c,9871c06,0654c0a]:v1.170.33Compare Source
Patch Changes
#8165
2f20c00- Exclude structural descendants below error and not-found boundaries from route lifecycle callbacks. Preserve lifecycle membership through invalidation, hydration, background reloads, and superseded navigation publication.#8209
28a5e45- Preserve falsy thrown values in React and Vue error boundaries. Type React and Vue boundary error components andonCatchcallbacks asunknown. Solid boundary errors remain typed asError; SSR now wraps non-Errorloader errors to match Solid’s native boundary behavior, preserving the original value incause. Router state and loaderonErrorvalues are unchanged.When upgrading React or Vue, narrow boundary errors (for example, with
error instanceof Error) before readingmessageorstack.ErrorComponentProps<TError>remains available for values narrowed to a specific error type. RouteonErrortypes are unchanged.#8161
f0b5eda- Retain successful not-found matches as terminal shared boundaries during client navigation, preserving route context while the destination loads.#8251
0497cae- Use URL.canParse for absolute URL checks in links, navigation, redirects, and build configuration. Preserve a URL constructor fallback for older browsers.#8169
0caf6b9- Fix route-scopeduseMatch,useSearch, anduseParamsAPIs to forward theshouldThrowoption and preserve optional return types whenshouldThrow: false.#8257
cf166d1- Fix repeatedinnerHTMLwrites for unchanged styles and data scripts during React re-renders. This prevents unnecessary CSS parsing and Trusted Types errors during client navigation.Updated dependencies [
edf0e16,2f20c00,28a5e45,08eff50,216c0c4,2f91503,f0b5eda,50eafca,0497cae,ee28348,9035abc,c18e690]:TanStack/router (@tanstack/react-router-devtools)
v1.167.2Compare Source
Patch Changes
d76a332,b747fb8,6cfb1e8,700a714,700a714,6387d58,7e349c3,9b2adaf,873c830,7e349c3,634da91,e9396c9,634da91,f151ab0,bc57fa3,6387d58,9872d2a,d76a332,634da91,634da91,7e349c3,9448caa,e9396c9,700a714,634da91,634da91]:vercel/ai (ai)
v7.0.100Compare Source
Patch Changes
6431635: feat(ai): expose typed AI SDK errors for UI transport and completion failures23a0fff]v7.0.99Compare Source
Patch Changes
615ac89: feat(ai): use InvalidArgumentError for utility input validation7f76d83]v7.0.98Compare Source
Patch Changes
5ec21a6: fix: reject unsupported batch request typesdb59d78: feat(ai): add runtime context attribution to embed, embedMany and rerank7469a3b: feat: support image generation requests in batchesf87bf07: fix(ai): reject invalid reranking provider indicesbc5cb7a: fix(ai): accept inferred tools invalidateUIMessagesa5f449a: feat(ai): add a stable UI message type and type guard for tool output errors5ec21a6]7469a3b]dbd83a3]813bb36]c43e4b7]03f4e59]v7.0.97Compare Source
Patch Changes
ef3bac4: Observe video webhook receiver rejections before generation starts to prevent unhandled rejections during or after a failed start. Preserve start error precedence and assimilate custom receivers only once.9942196: feat: add batch cancel and list APIs9942196]v7.0.96Compare Source
Patch Changes
912fb01: feat: add batch cancel and list APIsc595e6e: fix(ai): callatobwithout a receiver for Cloudflare Workers compatibility912fb01]aa4cc14](https://redirect.github.com/vConfiguration
📅 Schedule: (in timezone America/New_York)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, 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.