Update all non-major frontend-admin dependencies - #1765
Merged
Conversation
renovate
Bot
added
dependencies
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1765 +/- ##
=======================================
Coverage 93.42% 93.42%
=======================================
Files 76 76
Lines 2418 2418
Branches 190 190
=======================================
Hits 2259 2259
Misses 132 132
Partials 27 27 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/all-minor-patch-frontend-admin
branch
13 times, most recently
from
September 4, 2026 13:08
4eddec7 to
9fff0c9
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch-frontend-admin
branch
4 times, most recently
from
September 6, 2026 19:30
0dd62b8 to
525fbef
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch-frontend-admin
branch
from
September 6, 2026 19:35
209b77c to
5b654da
Compare
KOliver94
approved these changes
Sep 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.40.1→2.41.010.70.0→10.73.05.101.4→5.102.85.101.4→5.102.85.101.4→5.102.819.2.4→19.2.76.1.0→6.1.11.19.0→1.20.010.9.0→10.9.117.11.0→17.12.08.5.26→8.5.2810.9.8→10.9.97.85.0→7.87.08.3.0→8.3.18.67.0→8.69.0Release Notes
OpenAPITools/openapi-generator-cli (@openapitools/openapi-generator-cli)
v2.41.0Compare Source
Features
getsentry/sentry-javascript (@sentry/react)
v10.73.0Compare Source
Important Changes
feat(v10/nextjs): Add
@sentry/nextjs/configentry point (#23766)withSentryConfigis now available from@sentry/nextjs/config, the path it moves to in v11. Importing it from@sentry/nextjsstill works on v10 but logs a warning once, so you can change yournext.configfile today and upgrade to v11 without touching it again.Other Changes
shouldHandleErroronsetupExpressErrorHandlerandsetupFasitfyErrorHandler(#23734)Internal Changes
Bundle size 📦
v10.72.0Compare Source
Important Changes
AI integrations no longer report errors that propagate to the caller (#23638, #23639, #23640)
Across all AI integrations (OpenAI, Anthropic, Google GenAI, LangChain, and LangGraph), the SDK no longer sends an event to Sentry for errors that the AI framework propagates to your code. Previously the instrumentation reported these as unhandled (
handled: false) before your own error handling ran, so an error your code caught still showed up in Sentry as an unhandled crash. The span is still marked as errored and the error still propagates, so reporting is left to your application: if your code does not handle the error, it reaches Sentry's global error handlers and is captured as unhandled, just like any other uncaught error. Errors that a provider surfaces as data on an otherwise successful response (such as Anthropic error-shaped responses or Google GenAI blocked content) are still captured, since your code never sees them propagate.feat(v10/cloudflare): Add
rpcTracePropagationBindings(#23737, #23738)The new
rpcTracePropagationBindingsoption names theenvbindings that outgoing RPC calls propagate trace context to. Strings match a binding name exactly, regular expressions match by pattern, and the default empty array propagates to nothing. RPC has no headers to carry trace context, so the SDK appends it as a trailing argument that only a Sentry-instrumented receiver removes again. List only the bindings whose receiver you know runs Sentry. Setting the option takes precedence overenableRpcTracePropagation, which is now deprecated. When you build with the Sentry Cloudflare Vite plugin, the bindings that resolve to this worker (its own Durable Objects and self service bindings) are derived from your wrangler config and added for you.Other Changes
_childSpanTimeoutID(#23673)Internal Changes
Work in this release was contributed by @ryanrho-mercor, @lux-in-tenebris-lucet, and @suhailopensource. Thank you for your contributions!
Bundle size 📦
v10.71.0Compare Source
Important Changes
The
enableLogsclient option now defaults totrue, so Sentry Logs work without any manual opt-in. Nothing is captured unless you call theSentry.logger.*APIs or add a log-forwarding integration (such asconsoleLoggingIntegration,pinoIntegration, or the winston transport), and you can setenableLogs: falseto opt out. Although a default change like this would normally land in a major release, we are shipping it in a minor after careful consideration, since it sends no data on its own and only takes effect once you actively use the logging APIs or a logging integration.Other Changes
scope.clear()method (#23231)Headersinstances (#23241)captureExceptionfrom scope, not fromClient(#23280)Internal Changes
Bundle size 📦
TanStack/query (@tanstack/eslint-plugin-query)
v5.102.8Compare Source
v5.102.7Compare Source
v5.102.6Compare Source
v5.102.5Compare Source
v5.102.4Compare Source
v5.102.3Compare Source
v5.102.2Compare Source
v5.102.1Compare Source
v5.102.0Compare Source
Patch Changes
#11212
279bb55- TypeScript 7 compatibility#11188
3bc8edf- Fix false-positive warnings inno-unstable-depsrule caused byObject.prototypeproperty lookups (toString,valueOf, etc.).#11115
8582702- Remove unused helper functions from the internalASTUtilsobject (getNestedIdentifiers,getNestedReturnStatements,getClosestVariableDeclarator,mapKeyNodeToText, andmapKeyNodeToBaseText). They were not referenced by any rule and are not part of the public API.TanStack/query (@tanstack/react-query)
v5.102.8Compare Source
Patch Changes
v5.102.7Compare Source
Patch Changes
v5.102.6Compare Source
Patch Changes
#11305
ac2b612- fix(react-query): throw falsy errors fromuseQueriesanduseSuspenseQueriesto the error boundaryUpdated dependencies []:
v5.102.5Compare Source
Patch Changes
578e5c2]:v5.102.4Compare Source
Patch Changes
a05df6a]:v5.102.3Compare Source
Patch Changes
v5.102.2Compare Source
Patch Changes
80fbf73]:v5.102.1Compare Source
Patch Changes
134890d]:v5.102.0Compare Source
Minor Changes
e674826- react-query: update usePrefetchQuery and usePrefetchInfiniteQuery to use queryClient.query and queryClient.infiniteQueryPatch Changes
#11245
37127db- revert: remove NoInfer from useQuery return types#10373
6e3d521- fix(types): propagate generic type parameters touseMutationStateselect callback#11224
294d4e6- FixqueryOptionsandinfiniteQueryOptionsreturn types so exported inferred options can be emitted in declaration files without leaking internal data tag symbols.#11147
cb6c9d3- DefaultTDataofUseInfiniteQueryOptionsandUseSuspenseInfiniteQueryOptionstoInfiniteData<TQueryFnData>so it matches the hook generics.#8737
2215bb0- fix: make mutation variables optional whenundefined extends TVariables#11221
1ef4208- Remove experimental render-time prefetching and thepromiseproperty from query results.#11228
fb6c3fa- Avoid emitting a runtime import for React Query's type-only exports.#11130
8834267- fix(react-query): don't show optimistic fetching for unsubscribed useQueries#11233
b866a95- remove unused experimental_beforeQuery and experimental_afterQuery hooks#11144
e546d03- fix: remove placeholderData from suspense infinite queryUpdated dependencies [
34f7cee,b4368c4,5bb089d,ba4650c,294d4e6,1f631b3,01a02bf,18c1c1e,5448063,2215bb0,1ef4208,5981771,4a9bef6,bef4bc7,9656dc4,326aaf1,3e83601,c6fc17c]:TanStack/query (@tanstack/react-query-devtools)
v5.102.8Compare Source
Patch Changes
v5.102.7Compare Source
Patch Changes
v5.102.6Compare Source
Patch Changes
ac2b612]:v5.102.5Compare Source
Patch Changes
ef1eff1]:v5.102.4Compare Source
Patch Changes
v5.102.3Compare Source
Patch Changes
v5.102.2Compare Source
Patch Changes
v5.102.1Compare Source
Patch Changes
Configuration
📅 Schedule: (in timezone Europe/Budapest)
* * * * 0,6)🚦 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.