This repository was archived by the owner on Oct 5, 2026. It is now read-only.
Repository navigation
fix(deps): update non-breaking updates - #630
Closed
renovate[bot] wants to merge 1 commit into
Closed
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
renovate
Bot
force-pushed
the
renovate/non-breaking-updates
branch
13 times, most recently
from
July 27, 2026 19:41
c4df6a0 to
ae4bc08
Compare
renovate
Bot
force-pushed
the
renovate/non-breaking-updates
branch
14 times, most recently
from
August 2, 2026 05:52
13aca3b to
b8681bf
Compare
renovate
Bot
force-pushed
the
renovate/non-breaking-updates
branch
15 times, most recently
from
August 19, 2026 05:39
f858f60 to
b2bf4b3
Compare
renovate
Bot
force-pushed
the
renovate/non-breaking-updates
branch
10 times, most recently
from
August 26, 2026 19:07
dae8028 to
7616d2d
Compare
renovate
Bot
force-pushed
the
renovate/non-breaking-updates
branch
3 times, most recently
from
August 28, 2026 20:02
1d08b02 to
e4a9f06
Compare
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
^5.11.0→^5.11.4^2.1.0→^2.1.1^3.1.14→^3.3.73.3.8^2.20.2→^2.25.4^10.63.0→^10.75.010.76.0(+3)^7.1.2→^7.3.07.3.1^4.3.2→^4.3.3^2.7.1→^2.7.32.8.1(+1)^2.5.1→^2.5.22.6.0^2.5.4→^2.5.52.7.0(+1)^2.4.0→^2.4.12.5.0^2.10.1→^2.11.02.13.1(+2)^11.18.0→^11.19.0^24.13.2→^24.13.624.19.1(+1)^10.5.2→^10.6.1^5.6.13→^5.7.425.7.47(+4)^10.6.0→^10.11.010.12.0^3.20.0→^3.23.0^7.4.2→^7.5.0^17.7.0→^17.12.017.13.0^1.6.16→^1.7.30.4.33→0.4.34^18.0.5→^18.0.1318.0.14^3.9.4→^3.9.83.9.9^0.8.0→^0.8.1^25.0.5→^25.0.90.48.3→0.49.20.49.30.48.3→0.49.20.49.31.0.228→1.0.2291.0.150→1.0.151^5.56.4→^5.57.1^4.7.1→^4.7.6^4.3.2→^4.3.32.10.3→2.11.52.12.1(+2)2.7.1→2.7.32.8.1(+1)2.5.1→2.5.22.6.02.5.4→2.5.52.7.0(+1)2.4.0→2.4.12.5.02.10.1→2.11.02.13.1(+2)^8.62.1→^8.70.08.71.0(+1)^8.1.3→^8.3.08.3.2(+1)^4.4.3→^4.6.5Release Notes
eslint/rewrite (@eslint/compat)
v2.1.1Compare Source
Bug Fixes
opral/paraglide-js (@inlang/paraglide-js)
v2.25.4Patch Changes
afe6fdc: Fix default URL routing dropping trailing slashes when localizing or delocalizing paths. WhentrailingSlashis omitted,/about/now becomes/en/about/and/en/about/delocalizes to/about/, matching equivalent explicit URL patterns. Paths without trailing slashes and localized root behavior remain unchanged. SettrailingSlash: "never"to explicitly generate slashless URLs;"always"continues to enforce trailing slashes.v2.25.3Patch Changes
e1e6e61: Upgrade the inlang SDK to 3.0.6 with Lix 0.17.0.v2.25.2Patch Changes
b26bada: Upgrade Inlang SDK to 3.0.5 with Lix 0.16.1 to fix compilation of sorted message files above 512 tracked-state rows. Includes transaction error handling and snapshot restoration fixes.v2.25.1Patch Changes
845e819: Upgrade the Inlang SDK to 3.0.4, including Lix 0.15.1 fixes for transaction-local message and variant reads.v2.25.0Minor Changes
f719e1f: ExposecleanOutdir,experimentalStaticLocale, anddisableAsyncLocalStorageasparaglide-js compileCLI flags.5ed1745: Add support for aparaglide.config.js(or.mjs,.ts,.cjs)configuration file inside the inlang project directory.
The CLI and all bundler plugins now pick up compiler options from
<project>/paraglide.config.*. The project directory comes from--projector the plugin's
projectoption and defaults to the conventional./project.inlang— which means every bundler plugin can now beinstantiated without arguments. Since the config lives inside the project it
configures, it cannot set
projectitself. Explicit flags and pluginoptions win over the config file, which wins over the built-in defaults.
Existing setups keep working unchanged.
Also included:
defineConfighelper exported from@inlang/paraglide-jsfor typeinference and autocompletion in config files.
between the supported file names. Deleting all config files falls back to
the built-in defaults; an invalid config skips the compilation with an
error — watch modes keep serving the previous output, production builds
fail loudly. (esbuild does not support config watching.)
cleanOutdiris accepted but ignored: watch integrations always preservethe output directory for incremental compilation.
Patch Changes
aa4ffd3: Resolve references to earlier local variables correctly in message declarations and formatter options.3634877: FixexperimentalMiddlewareLocaleSplittingcorrupting the generated server file when a compiled message value contains a literal$(e.g. a price or currency symbol) that forms aString.replace()special replacement pattern such as$`.1bacc27: FixexperimentalMiddlewareLocaleSplittingkeyingcompiledBundlesby the raw bundle id instead of the safe module id, so every SSR message lookup missed and threwglobalThis.__paraglide.ssr.<id> is not a functionon hydration.v2.24.1Patch Changes
d2aeb93: Update the inlang SDK dependency to 3.0.1, which includes the Lix WASM fallback for musl-based Node.js environments.v2.24.0Minor Changes
7028c8a: Upgrade to@inlang/sdkv3 and remove obsolete local account migration code.Patch Changes
0ac907e: Cache compiled URL patterns to speed up repeated localized-link generation.fda90d2: Skip unchanged Vite compilations across dev-server restarts by persisting and validating the compiler input cache.84e2766: Add a fast path for common locale-prefix and static-domain URL patterns while preserving the generic URLPattern fallback.5de9441: Improve compiler output writes by using Node's synchronous SHA-256 implementation and only creating directories for generated files that changed.5c17acf: Allow importing the programmatic compiler API without installing the optional Vite peer dependency.c52b523: Preserve request bodies inparaglideMiddlewareby cloning body-bearing requests before rewrapping them, preventing "Body has already been read" errors on POST/PUT/PATCH/DELETE.32d285b: Avoid rewriting unchanged output files during one-shot CLI compilation.9e1ee2e: Add an opt-intrailingSlashcompiler option for canonicalizing localized URLs.v2.23.2Patch Changes
b8af4b1: Embed TypeScript sources in published JavaScript sourcemaps and stop emitting declaration sourcemaps that reference unpublished source files.v2.23.1Patch Changes
6f9b062: Keep the server middleware's AsyncLocalStorage available when module instrumentation snapshots mutable exports.v2.23.0Minor Changes
c2b9c17: Replace the experimental per-locale framework-output specialization with aVite 8+ environment architecture.
experimentalPerLocaleBuild: truenowgenerates locale source modules before bundling, builds independent native
Rolldown graphs, supports unminified builds and source maps, and emits
paraglide-vite-locales.jsonwithout rewriting completed chunks or frameworkoutput.
Remove the private TanStack Start and SvelteKit renderer integrations. Those
frameworks now require public client-variant build and render-selection APIs
before they can compose with experimental per-locale builds.
Patch Changes
608385f: UsebaseLocaleas the exhaustive branch in generated message functions.getsentry/sentry-javascript (@sentry/sveltekit)
v10.75.0Compare Source
Important Changes
feat(v10/effect): Capture errors through the Effect v4
ErrorReporterAPI (#24445)On Effect v4,
Sentry.effectLayernow registers a SentryErrorReporter. Failures that pass throughEffect.withErrorReporting,ErrorReporter.reportor the built-in HTTP and RPC reporting boundaries are captured automatically, withErrorReporter.ignore,ErrorReporter.severityandErrorReporter.attributesannotations respected. Nothing changes on Effect v3.Other Changes
CollectBehaviorshorthand fordataCollection.httpHeaders(#24339)virtualErroronce the request completed (#24307)disable-uploadis set (#24332)Bundle size 📦
v10.74.0Compare Source
user_agent.originalon all spans for consistent filtering (#24226)loadModuledefault parameter against ESM scope (#24154)DEFAULT_IGNORE_ERRORS(#23877)Internal Changes
Work in this release was contributed by @halillusion and @zkasuran. Thank you for your contributions!
Bundle size 📦
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)Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 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.