Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependencies (major) #492

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 9, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@hookform/resolvers (source) 3.9.1 -> 4.1.0 age adoption passing confidence
@sentry/nextjs (source) 8.52.0 -> 9.1.0 age adoption passing confidence
tailwind-merge 2.5.4 -> 3.0.1 age adoption passing confidence

Release Notes

react-hook-form/resolvers (@​hookform/resolvers)

v4.1.0

Compare Source

Features

v4.0.0

Compare Source

Bug Fixes
  • add support for names option (#​713) (985c48d)
  • arktypeResolver: resolve type error when schema is defined from an ArkType scope (#​732) (3233667)
  • handle raw: true option to pass form submission values correctly (#​733) (7807f95)
  • validateFieldsNatively: handle undefined object when reading 'refs' (#​734) (3da2054)
Features
  • ajv: Keep original validation type while using errorMessage (#​728) (5030a59)
  • effectResolver: returns either all errors or only the first one based on criteriaMode (#​737) (12d7d8e)
  • standard-schema: add standard-schema resolver (#​738) (b75a95a)
BREAKING CHANGES
  • ajv: The AJV Resolver now unwraps the errorMessage object to return the original error types. This update may introduce breaking changes to your projects.

v3.10.0

Compare Source

Features
getsentry/sentry-javascript (@​sentry/nextjs)

v9.1.0

Compare Source

Work in this release was contributed by @​Zen-cronic and @​filips-alpe. Thank you for your contribution!

v9.0.1

Compare Source

  • ref(flags): rename unleash integration param (#​15343)

v9.0.0

Compare Source

Version 9.0.0 marks a release of the Sentry JavaScript SDKs that contains breaking changes.
The goal of this release is to trim down on unused and potentially confusing APIs, prepare the SDKs for future framework versions to build deeper instrumentation, and remove old polyfills to reduce the packages' size.

How To Upgrade

Please carefully read through the migration guide in the Sentry docs on how to upgrade from version 8 to version 9.
Make sure to select your specific platform/framework in the top left corner: https://docs.sentry.io/platforms/javascript/migration/v8-to-v9/

A comprehensive migration guide outlining all changes for all the frameworks can be found within the Sentry JavaScript SDK Repository: https://github.com/getsentry/sentry-javascript/blob/develop/MIGRATION.md

Breaking Changes
  • doc(deno)!: Make Deno v2 the minimum supported version (#​15085)
  • feat!: Bump typescript to ~5.0.0 (#​14758)
  • feat!: Drop nitro-utils package (#​14998)
  • feat!: Only collect ip addresses with sendDefaultPii: true (#​15084)
  • feat!: Remove autoSessionTracking option (#​14802)
  • feat!: Remove enableTracing (#​15078)
  • feat!: Remove getCurrentHub(), Hub, and getCurrentHubShim() (#​15122)
  • feat!: Remove spanId from propagation context (#​14733)
  • feat!: Remove deprecated and unused code (#​15077)
  • feat!: Remove metrics API from the JS SDK (#​14745)
  • feat!: Require Node >=18 as minimum supported version (#​14749)
  • feat(astro)!: Respect user-specified source map setting (#​14941)
  • feat(browser)!: Remove captureUserFeedback method (#​14820)
  • feat(build)!: Drop pre-ES2020 polyfills (#​14882)
  • feat(core)!: Add normalizedRequest to samplingContext (#​14902)
  • feat(core)!: Always use session from isolation scope (#​14860)
  • feat(core)!: Pass root spans to beforeSendSpan and disallow returning null (#​14831)
  • feat(core)!: Remove BAGGAGE_HEADER_NAME export (#​14785)
  • feat(core)!: Remove TransactionNamingScheme type (#​14865)
  • feat(core)!: Remove addOpenTelemetryInstrumentation method (#​14792)
  • feat(core)!: Remove arrayify method (#​14782)
  • feat(core)!: Remove debugIntegration and sessionTimingIntegration (#​14747)
  • feat(core)!: Remove flatten method (#​14784)
  • feat(core)!: Remove getDomElement method (#​14797)
  • feat(core)!: Remove makeFifoCache method (#​14786)
  • feat(core)!: Remove memoBuilder export & WeakSet fallback (#​14859)
  • feat(core)!: Remove transactionContext from samplingContext (#​14904)
  • feat(core)!: Remove urlEncode method (#​14783)
  • feat(core)!: Remove deprecated Request type (#​14858)
  • feat(core)!: Remove deprecated request data methods (#​14896)
  • feat(core)!: Remove standalone Client interface & deprecate BaseClient (#​14800)
  • feat(core)!: Remove validSeverityLevels export (#​14765)
  • feat(core)!: Stop accepting event as argument for recordDroppedEvent (#​14999)
  • feat(core)!: Stop setting user in requestDataIntegration (#​14898)
  • feat(core)!: Type sdkProcessingMetadata more strictly (#​14855)
  • feat(core)!: Update hasTracingEnabled to consider empty trace config (#​14857)
  • feat(core)!: Update requestDataIntegration handling (#​14806)
  • feat(deno)!: Remove deno prepack (#​14829)
  • feat(ember)!: Officially drop support for ember <=3.x (#​15032)
  • feat(nestjs)!: Move nestIntegration into nest sdk and remove setupNestErrorHandler (#​14751)
  • feat(nestjs)!: Remove @WithSentry decorator (#​14762)
  • feat(nestjs)!: Remove SentryService (#​14759)
  • feat(nextjs)!: Don't rely on Next.js Build ID for release names (#​14939)
  • feat(nextjs)!: Remove experimental_captureRequestError (#​14607)
  • feat(nextjs)!: Respect user-provided source map generation settings (#​14956)
  • feat(node)!: Add support for Prisma v6 and drop v5 support (#​15120)
  • feat(node)!: Avoid http spans by default for custom OTEL setups (#​14678)
  • feat(node)!: Collect request sessions via HTTP instrumentation (#​14658)
  • feat(node)!: Remove processThreadBreadcrumbIntegration (#​14666)
  • feat(node)!: Remove fine grained registerEsmLoaderHooks (#​15002)
  • feat(opentelemetry)!: Exclusively pass root spans through sampling pipeline (#​14951)
  • feat(pinia)!: Include state of all stores in breadcrumb (#​15312)
  • feat(react)!: Raise minimum supported TanStack Router version to 1.63.0 (#​15030)
  • feat(react)!: Remove deprecated getNumberOfUrlSegments method (#​14744)
  • feat(react)!: Remove deprecated react router methods (#​14743)
  • feat(react)!: Update ErrorBoundary componentStack type (#​14742)
  • feat(remix)!: Drop support for Remix v1 (#​14988)
  • feat(remix)!: Remove autoInstrumentRemix option (#​15074)
  • feat(solidstart)!: Default to --import setup and add autoInjectServerSentry (#​14862)
  • feat(solidstart)!: No longer export sentrySolidStartVite (#​15143)
  • feat(solidstart)!: Respect user-provided source map setting (#​14979)
  • feat(svelte)!: Disable component update tracking by default (#​15265)
  • feat(sveltekit)!: Drop support for SvelteKit @​1.x (#​15037)
  • feat(sveltekit)!: Remove fetchProxyScriptNonce option (#​15123)
  • feat(sveltekit)!: Respect user-provided source map generation settings (#​14886)
  • feat(utils)!: Remove @sentry/utils package (#​14830)
  • feat(vue)!: Remove configuring Vue tracing options anywhere else other than through the vueIntegration's tracingOptions option (#​14856)
  • feat(vue/nuxt)!: No longer create "update" spans for component tracking by default (#​14602)
  • fix(node)!: Fix name of vercelAIIntegration to VercelAI (#​15298)
  • fix(vue)!: Remove logError from vueIntegration (#​14958)
  • ref!: Don't polyfill optional chaining and nullish coalescing (#​14603)
  • ref(core)!: Cleanup internal types, including ReportDialogOptions (#​14861)
  • ref(core)!: Mark exceptions from captureConsoleIntegration as handled: true by default (#​14734)
  • ref(core)!: Move shutdownTimeout option type from core to node (#​15217)
  • ref(core)!: Remove Scope type interface in favor of using Scope class (#​14721)
  • ref(core)!: Remove backwards compatible SentryCarrier type (#​14697)
Other Changes

Work in this release was contributed by @​aloisklink, @​arturovt, @​aryanvdesh, @​benjick, @​chris-basebone, @​davidturissini, @​GrizliK1988, @​jahands, @​jrandolf, @​kunal-511, @​maximepvrt, @​maxmaxme, @​mstrokin, @​nathankleyn, @​nwalters512, @​tannerlinsley, @​tjhiggins, and @​Zen-cronic. Thank you for your contributions!

v8.55.0

Compare Source

Important Changes
  • chore(ci/v8): Switch lambda layer name to SentryNodeServerlessSDKv8 (#​15351)

The SentryNodeServerlessSDK AWS Lambda Layer will stop receiving updates.
If you intend to stay on v8 and receive updates use SentryNodeServerlessSDKv8 instead.

Other Changes
  • feat(flags/v8): add Statsig browser integration (#​15347)
  • feat(v8/node): Add missing vercelAIIntegration export (#​15339)
  • feat(v8/nuxt): Add enabled to disable Sentry module (#​15337) (#​15381)
  • feat(v8/vue): Support Pinia v3 (#​15384)
  • fix(astro): Add vue to registerEsmLoaderHooks (#​15352)
  • fix(react/v8): Support lazy-loaded routes and components (#​15281)
  • fix(v8/nuxt): Detect Azure Function runtime for flushing with timeout (#​15297)
  • fix(v8/solidstart): Do not copy release-injection map file (#​15304)
  • fix(v8/svelte): Guard component tracking beforeUpdate call (#​15262)

Work in this release was contributed by @​aryanvdesh. Thank you for your contribution!

Bundle size 📦
Path Size
@​sentry/browser 23.3 KB
@​sentry/browser - with treeshaking flags 23.17 KB
@​sentry/browser (incl. Tracing) 35.9 KB
@​sentry/browser (incl. Tracing, Replay) 73.27 KB
@​sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.71 KB
@​sentry/browser (incl. Tracing, Replay with Canvas) 77.57 KB
@​sentry/browser (incl. Tracing, Replay, Feedback) 89.5 KB
@​sentry/browser (incl. Feedback) 39.51 KB
@​sentry/browser (incl. sendFeedback) 27.91 KB
@​sentry/browser (incl. FeedbackAsync) 32.71 KB
@​sentry/react 25.98 KB
@​sentry/react (incl. Tracing) 38.71 KB
@​sentry/vue 27.58 KB
@​sentry/vue (incl. Tracing) 37.75 KB
@​sentry/svelte 23.46 KB
CDN Bundle 24.49 KB
CDN Bundle (incl. Tracing) 37.6 KB
CDN Bundle (incl. Tracing, Replay) 72.9 KB
CDN Bundle (incl. Tracing, Replay, Feedback) 78.23 KB
CDN Bundle - uncompressed 71.92 KB
CDN Bundle (incl. Tracing) - uncompressed 111.52 KB
CDN Bundle (incl. Tracing, Replay) - uncompressed 225.78 KB
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 238.88 KB
@​sentry/nextjs (client) 38.96 KB
@​sentry/sveltekit (client) 36.4 KB
@​sentry/node 162.85 KB
@​sentry/node - without tracing 99.14 KB
@​sentry/aws-serverless 131.23 KB

v8.54.0

Compare Source

  • feat(v8/deps): Upgrade all OpenTelemetry dependencies (#​15098)
  • fix(node/v8): Add compatibility layer for Prisma v5 (#​15210)

Work in this release was contributed by @​nwalters512. Thank you for your contribution!

v8.53.0

Compare Source

  • feat(v8/nuxt): Add url to SourcemapsUploadOptions (#​15202)
  • fix(v8/react): fromLocation can be undefined in Tanstack Router Instrumentation (#​15237)

Work in this release was contributed by @​tannerlinsley. Thank you for your contribution!

v8.52.1

Compare Source

  • fix(v8/nextjs): Fix nextjs build warning (#​15226)
  • ref(v8/browser): Add protocol attributes to resource spans #​15224
  • ref(v8/core): Don't set this.name to new.target.prototype.constructor.name (#​15222)

Work in this release was contributed by @​Zen-cronic. Thank you for your contribution!

dcastil/tailwind-merge (tailwind-merge)

v3.0.1

Compare Source

Bug Fixes

Full Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.0

Compare Source

Tailwind CSS v4 is here and it's time to upgrade tailwind-merge to support it. tailwind-merge v3.0.0 is more accurate than ever and follows the Tailwind CSS spec more closely than in v2. That is thanks to Tailwind CSS v4 being more consistent than ever.

This release drops support for Tailwind CSS v3 and in turn adds support for Tailwind CSS v4. That means you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together. All breaking changes are related to the Tailwind CSS v4 support.

Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes
New Features
Bug Fixes
Documentation

Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and a private sponsor for sponsoring tailwind-merge! ❤️

v2.6.0

Compare Source

New Features

Full Changelog: dcastil/tailwind-merge@v2.5.5...v2.6.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph, a private sponsor and more via @​thnxdev for sponsoring tailwind-merge! ❤️

v2.5.5

Compare Source

Bug Fixes
Documentation

Full Changelog: dcastil/tailwind-merge@v2.5.4...v2.5.5

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov and more via @​thnxdev for sponsoring tailwind-merge! ❤️


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Copy link

vercel bot commented Feb 9, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
translo ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 9, 2025 5:39pm

@renovate renovate bot changed the title chore(deps): update dependency tailwind-merge to v3 chore(deps): update dependencies (major) Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants