chore(deps): update all non-major dependencies #174
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
19 times, most recently
from
699fe74 to
5289d06
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
d93ec18 to
4aaa640
Compare
|
Blocking by vuejs/language-tools#5020 |
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
5 times, most recently
from
290748f to
e93236f
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
994da75 to
173e4a7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
173e4a7 to
fd55de4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^9.15.0->^9.16.0^8.39.0->^8.45.0^22.9.1->^22.10.2^0.64.1->^0.65.1^0.64.1->^0.65.1^0.64.1->^0.65.1^5.2.0->^5.2.1^6.21.0->^6.22.0^9.15.0->^9.16.0^4.4.3->^4.5.0^9.31.0->^9.32.0^15.12.0->^15.13.0^14.4.4->^14.4.5^15.2.10->^15.2.11^2.40.1->^2.40.39.14.2->9.15.0^3.3.3->^3.4.2^5.36.0->^5.37.0^5.6.3->^5.7.28.15.0->8.18.0^0.64.1->^0.65.1Release Notes
eslint/eslint (@eslint/js)
v9.16.0Compare Source
getsentry/sentry-javascript (@sentry/browser)
v8.45.0Compare Source
handledoption tocaptureConsoleIntegration(#14664)HttpClientevents (#14515)captureMessagewithattachStacktrace: trueas synthetic (#14668)captureMessagewithattatchStackTrace: trueas synthetic (#14670)levelin server runtimecaptureException(#10587)Work in this release was contributed by @anonrig and @Zih0. Thank you for your contributions!
Bundle size 📦
v8.44.0Compare Source
Deprecations
feat: Deprecate
autoSessionTracking(#14640)Deprecates
autoSessionTracking.To enable session tracking, it is recommended to unset
autoSessionTrackingand ensure that either, in browser environmentsthe
browserSessionIntegrationis added, or in server environments thehttpIntegrationis added.To disable session tracking, it is recommended to unset
autoSessionTrackingand to remove thebrowserSessionIntegrationinbrowser environments, or in server environments configure the
httpIntegrationwith thetrackIncomingRequestsAsSessionsoption set tofalse.Other Changes
responsecontext for http.server spans (#14634)Work in this release was contributed by @robinvw1. Thank you for your contribution!
Bundle size 📦
v8.43.0Compare Source
Important Changes
feat(nuxt): Add option autoInjectServerSentry (no default import()) (#14553)
Using the dynamic
import()as the default behavior for initializing the SDK on the server-side did not work for every project.The default behavior of the SDK has been changed, and you now need to use the
--importflag to initialize Sentry on the server-side to leverage full functionality.Example with
--import:In case you are not able to use the
--importflag, you can enable auto-injecting Sentry in thenuxt.config.ts(comes with limitations):feat(browser): Adds LaunchDarkly and OpenFeature integrations (#14207)
Adds browser SDK integrations for tracking feature flag evaluations through the LaunchDarkly JS SDK and OpenFeature Web SDK:
feat(browser): Add
featureFlagsIntegrationfor custom tracking of flag evaluations (#14582)Adds a browser integration to manually track feature flags with an API. Feature flags are attached to subsequent error events:
feat(astro): Add Astro 5 support (#14613)
With this release, the Sentry Astro SDK officially supports Astro 5.
Deprecations
feat(nextjs): Deprecate typedef for
hideSourceMaps(#14594)The functionality of
hideSourceMapswas removed in version 8 but was forgotten to be deprecated and removed.It will be completely removed in the next major version.
feat(core): Deprecate APIs around
RequestSessions (#14566)The APIs around
RequestSessions are mostly used internally.Going forward the SDK will not expose concepts around
RequestSessions.Instead, functionality around server-side Release Health will be managed in integrations.
Other Changes
browserSessionIntegration(#14551)raw_securityenvelope types (#14562)disableAnrDetectionForCallbackfunction (#14359)trackIncomingRequestsAsSessionsoption to http integration (#14567)autoInjectServerSentry(no defaultimport()) (#14553)^1.29.0(#14590)1.28.0(#14547)filenameandmodulestack frame properties in Node stack parser (#14544)maxSpanWaitDurationvalues (#14632)parseSearchoption in TanStack Router instrumentation (#14328)Work in this release was contributed by @lsmurray. Thank you for your contribution!
Bundle size 📦
v8.42.0Compare Source
Important Changes
feat(react): React Router v7 support (library) (#14513)
This release adds support for React Router v7 (library mode).
Check out the docs on how to set up the integration: Sentry React Router v7 Integration Docs
Deprecations
feat: Warn about source-map generation (#14533)
In the next major version of the SDK we will change how source maps are generated when the SDK is added to an application.
Currently, the implementation varies a lot between different SDKs and can be difficult to understand.
Moving forward, our goal is to turn on source maps for every framework, unless we detect that they are explicitly turned off.
Additionally, if we end up enabling source maps, we will emit a log message that we did so.
With this particular release, we are emitting warnings that source map generation will change in the future and we print instructions on how to prepare for the next major.
feat(nuxt): Deprecate
tracingOptionsin favor ofvueIntegration(#14530)Currently it is possible to configure tracing options in two places in the Sentry Nuxt SDK:
Sentry.init()tracingOptionsinSentry.init()For tree-shaking purposes and alignment with the Vue SDK, it is now recommended to instead use the newly exported
vueIntegration()and itstracingOptionsoption to configure tracing options in the Nuxt SDK:Other Changes
web-vitalsto v4.2.4 (#14439)vueIntegration(#14526)Bundle size 📦
v8.41.0Compare Source
Important Changes
meta(nuxt): Require minimum Nuxt v3.7.0 (#14473)
We formalized that the Nuxt SDK is at minimum compatible with Nuxt version 3.7.0 and above.
Additionally, the SDK requires the implicit
nitropackdependency to satisfy version^2.10.0andofetchto satisfy^1.4.0.It is recommended to check your lock-files and manually upgrade these dependencies if they don't match the version ranges.
Deprecations
We are deprecating a few APIs which will be removed in the next major.
The following deprecations will potentially affect you:
feat(core): Update & deprecate
undefinedoption handling (#14450)In the next major version we will change how passing
undefinedtotracesSampleRate/tracesSampler/enableTracingwill behave.Currently, doing the following:
Will result in tracing being enabled (although no spans will be generated) because the
tracesSampleRatekey is present in the options object.In the next major version, this behavior will be changed so that passing
undefined(or rather having atracesSampleRatekey) will result in tracing being disabled, the same as not passing the option at all.If you are currently relying on
undefinedbeing passed, and and thus have tracing enabled, it is recommended to update your config to set e.g.tracesSampleRate: 0instead, which will also enable tracing in v9.The same applies to
tracesSamplerandenableTracing.feat(core): Log warnings when returning
nullinbeforeSendSpan(#14433)Currently, the
beforeSendSpanoption inSentry.init()allows you to drop individual spans from a trace by returningnullfrom the hook.Since this API lends itself to creating "gaps" inside traces, we decided to change how this API will work in the next major version.
With the next major version the
beforeSendSpanAPI can only be used to mutate spans, but no longer to drop them.With this release the SDK will warn you if you are using this API to drop spans.
Instead, it is recommended to configure instrumentation (i.e. integrations) directly to control what spans are created.
Additionally, with the next major version, root spans will also be passed to
beforeSendSpan.feat(utils): Deprecate
@sentry/utils(#14431)With the next major version the
@sentry/utilspackage will be merged into the@sentry/corepackage.It is therefore no longer recommended to use the
@sentry/utilspackage.feat(vue): Deprecate configuring Vue tracing options anywhere else other than through the
vueIntegration'stracingOptionsoption (#14385)Currently it is possible to configure tracing options in various places in the Sentry Vue SDK:
Sentry.init()tracingOptionsinSentry.init()vueIntegration()optionstracingOptionsin thevueIntegration()optionsBecause this is a bit messy and confusing to document, the only recommended way to configure tracing options going forward is through the
tracingOptionsin thevueIntegration().The other means of configuration will be removed in the next major version of the SDK.
feat: Deprecate
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.exclude(#14486)Currently it is possible to define
registerEsmLoaderHooks.includeandregisterEsmLoaderHooks.excludeoptions inSentry.init()to only apply ESM loader hooks to a subset of modules.This API served as an escape hatch in case certain modules are incompatible with ESM loader hooks.
Since this API was introduced, a way was found to only wrap modules that there exists instrumentation for (meaning a vetted list).
To only wrap modules that have instrumentation, it is recommended to instead set
registerEsmLoaderHooks.onlyIncludeInstrumentedModulestotrue.Note that
onlyIncludeInstrumentedModules: truewill become the default behavior in the next major version and theregisterEsmLoaderHookswill no longer accept fine-grained options.The following deprecations will most likely not affect you unless you are building an SDK yourself:
arrayify(#14405)flatten(#14454)urlEncode(#14406)validSeverityLevels(#14407)getNumberOfUrlSegments(#14458)memoBuilder,BAGGAGE_HEADER_NAME, andmakeFifoCache(#14434)addRequestDataToEventandextractRequestData(#14430)Other Changes
sentry-trace,baggageand DSC handling (#14364)openTelemetryInstrumentationsoption (#14484)NEXT_REDIRECTfrom browser (#14440)Work in this release was contributed by @NEKOYASAN and @fmorett. Thank you for your contributions!
Bundle size 📦
v8.40.0Compare Source
Important Changes
feat(angular): Support Angular 19 (#14398)
The
@sentry/angularSDK can now be used with Angular 19. If you're upgrading to the new Angular version, you might want to migrate from the now deprecatedAPP_INITIALIZERtoken toprovideAppInitializer.In this case, change the Sentry
TraceServiceinitialization inapp.config.ts:feat(core): Deprecate
debugIntegrationandsessionTimingIntegration(#14363)The
debugIntegrationwas deprecated and will be removed in the next major version of the SDK.To log outgoing events, use Hook Options (
beforeSend,beforeSendTransaction, ...).The
sessionTimingIntegrationwas deprecated and will be removed in the next major version of the SDK.To capture session durations alongside events, use [Context](https://docs.sentry.
Configuration
📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.