renovate[bot]
commented
4 months ago ⚠️ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: app/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@7.5.0
npm error Found: eslint@9.5.0
npm error node_modules/eslint
npm error eslint@"^9.0.0" from the root project
npm error peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error node_modules/@eslint-community/eslint-utils
npm error @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@7.5.0
npm error node_modules/@typescript-eslint/utils
npm error @typescript-eslint/utils@"7.5.0" from @typescript-eslint/eslint-plugin@7.5.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm error 1 more (@typescript-eslint/type-utils)
npm error @eslint-community/eslint-utils@"^4.2.0" from eslint@9.5.0
npm error 2 more (eslint-config-prettier, eslint-import-resolver-typescript)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.56.0" from @typescript-eslint/eslint-plugin@7.5.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error peer eslint@"^8.56.0" from @typescript-eslint/eslint-plugin@7.5.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error dev @typescript-eslint/eslint-plugin@"7.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-06-15T13_18_55_108Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-06-15T13_18_55_108Z-debug-0.log
This PR contains the following updates:
7.109.0->8.9.214.2.2->16.0.0^8.0.0->^9.0.0Release Notes
getsentry/sentry-javascript (@sentry/nextjs)
### [`v8.9.2`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#892) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.9.1...8.9.2) - fix(profiling): Update exports so types generate properly ([#12469](https://togithub.com/getsentry/sentry-javascript/issues/12469)) ### [`v8.9.1`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#891) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.8.0...8.9.1) ##### Important changes - **feat(solid): Add Solid SDK** This release adds a dedicated SDK for [Solid JS](https://www.solidjs.com/) in alpha state with instrumentation for [Solid Router](https://docs.solidjs.com/solid-router) and a custom `ErrorBoundary`. See the [package README](https://togithub.com/getsentry/sentry-javascript/blob/develop/packages/solid/README.md) for how to use the SDK. ##### Other changes - feat(deps): bump [@opentelemetry/instrumentation-express](https://togithub.com/opentelemetry/instrumentation-express) from 0.40.0 to 0.40.1 ([#12438](https://togithub.com/getsentry/sentry-javascript/issues/12438)) - feat(deps): bump [@opentelemetry/instrumentation-mongodb](https://togithub.com/opentelemetry/instrumentation-mongodb) from 0.44.0 to 0.45.0 ([#12439](https://togithub.com/getsentry/sentry-javascript/issues/12439)) - feat(deps): bump [@opentelemetry/propagator-aws-xray](https://togithub.com/opentelemetry/propagator-aws-xray) from 1.24.1 to 1.25.0 ([#12437](https://togithub.com/getsentry/sentry-javascript/issues/12437)) - feat(nextjs): Allow for suppressing warning about missing global error handler file ([#12369](https://togithub.com/getsentry/sentry-javascript/issues/12369)) - feat(redis): Add cache logic for redis-4 ([#12429](https://togithub.com/getsentry/sentry-javascript/issues/12429)) - feat(replay): Replay Web Vital Breadcrumbs ([#12296](https://togithub.com/getsentry/sentry-javascript/issues/12296)) - fix: Fix types export order ([#12404](https://togithub.com/getsentry/sentry-javascript/issues/12404)) - fix(astro): Ensure server-side exports work correctly ([#12453](https://togithub.com/getsentry/sentry-javascript/issues/12453)) - fix(aws-serverless): Add `op` to Otel-generated lambda function root span ([#12430](https://togithub.com/getsentry/sentry-javascript/issues/12430)) - fix(aws-serverless): Only auto-patch handler in CJS when loading `awslambda-auto` ([#12392](https://togithub.com/getsentry/sentry-javascript/issues/12392)) - fix(aws-serverless): Only start root span in Sentry wrapper if Otel didn't wrap handler ([#12407](https://togithub.com/getsentry/sentry-javascript/issues/12407)) - fix(browser): Fix INP span creation & transaction tagging ([#12372](https://togithub.com/getsentry/sentry-javascript/issues/12372)) - fix(nextjs): correct types conditional export ordering ([#12355](https://togithub.com/getsentry/sentry-javascript/issues/12355)) - fix(replay): Fix guard for exception event ([#12441](https://togithub.com/getsentry/sentry-javascript/issues/12441)) - fix(vue): Handle span name assignment for nested routes in VueRouter ([#12398](https://togithub.com/getsentry/sentry-javascript/issues/12398)) Work in this release was contributed by [@soch4n](https://togithub.com/soch4n). Thank you for your contribution! ### [`v8.8.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#880) [Compare Source](https://togithub.com/getsentry/sentry-javascript/compare/8.7.0...8.8.0) - **feat: Upgrade OTEL dependencies ([#12388](https://togithub.com/getsentry/sentry-javascript/issues/12388))** This upgrades the OpenTelemetry dependencies to the latest versions and makes OTEL use `import-in-the-middle` `v1.8.0`. This should fix numerous issues with using OTEL instrumentation with ESM. High level issues fixed with OTEL + ESM: - incompatibilities with using multiple loaders, commonly encountered while using `tsx` or similar libraries. - incompatibilities with libraries that use duplicate namespace exports like `date-fns`. - incompatibilities with libraries that use self-referencing namespace imports like `openai`. - incompatibilities with dynamic export patterns like exports with function calls. - `ENOENT: no such file or directory` bugs that libraries like [`discord.js`](https://togithub.com/discordjs/discord.js) surface. If you are still encountering issues with OpenTelemetry instrumentation and ESM, please let us know. - deps: Bump Sentry bundler plugins to version `2.18.0` ([#12381](https://togithub.com/getsentry/sentry-javascript/issues/12381)) - feat: Add `thirdPartyErrorFilterIntegration` ([#12267](https://togithub.com/getsentry/sentry-javascript/issues/12267)) - feat(core): Filter out error events with exception values and no stacktraces, values, or types ([#12387](https://togithub.com/getsentry/sentry-javascript/issues/12387)) - feat(core): Ignore additional common but inactionable errors ([#12384](https://togithub.com/getsentry/sentry-javascript/issues/12384)) - feat(deps): Bump [@opentelemetry/propagator-aws-xray](https://togithub.com/opentelemetry/propagator-aws-xray) from 1.3.1 to 1.24.1 ([#12333](https://togithub.com/getsentry/sentry-javascript/issues/12333)) - feat(deps): Bump [@sentry/cli](https://togithub.com/sentry/cli) from 2.31.2 to 2.32.1 ([#12332](https://togithub.com/getsentry/sentry-javascript/issues/12332)) - feat(redis): Support `mget` command in caching functionality ([#12380](https://togithub.com/getsentry/sentry-javascript/issues/12380)) - feat(vercel-edge): Export core integrations from Vercel edge SDK ([#12308](https://togithub.com/getsentry/sentry-javascript/issues/12308)) - fix(browser): Fix idle span ending ([#12306](https://togithub.com/getsentry/sentry-javascript/issues/12306)) - fix(browser): Fix parenthesis parsing logic for chromium ([#12373](https://togithub.com/getsentry/sentry-javascript/issues/12373)) - fix(browser): Fix types export path for CJS ([#12305](https://togithub.com/getsentry/sentry-javascript/issues/12305)) - fix(feedback): Override TriggerLabel Option ([#12316](https://togithub.com/getsentry/sentry-javascript/issues/12316)) - fix(feedback): Wait for document to be ready before doing autoinject ([#12294](https://togithub.com/getsentry/sentry-javascript/issues/12294)) - fix(nextjs): Fix memory leak ([#12335](https://togithub.com/getsentry/sentry-javascript/issues/12335)) - fix(nextjs): Fix version detection and option insertion logic for `clientTraceMetadata` option ([#12323](https://togithub.com/getsentry/sentry-javascript/issues/12323)) - fix(nextjs): Update argument name in log message about `sentry` property on Next.js config object ([#12366](https://togithub.com/getsentry/sentry-javascript/issues/12366)) - fix(node): Do not manually finish / update root Hapi spans. ([#12287](https://togithub.com/getsentry/sentry-javascript/issues/12287)) - fix(node): Fix virtual parent span ID handling & update create-next-app E2E test ([#12368](https://togithub.com/getsentry/sentry-javascript/issues/12368)) - fix(node): Skip capturing Hapi Boom responses v8. ([#12288](https://togithub.com/getsentry/sentry-javascript/issues/12288)) - fix(performance): Fix LCP not getting picked up on initial pageload transaction by setting reportAllChanges to true ([#12360](https://togithub.com/getsentry/sentry-javascript/issues/12360)) - fix(replay): Avoid infinite loop of logs ([#12309](https://togithub.com/getsentry/sentry-javascript/issues/12309)) - fix(replay): Ignore old events when manually starting replay ([#12349](https://togithub.com/getsentry/sentry-javascript/issues/12349)) - ref(browser): Ensure idle span ending is consistent ([#12310](https://togithub.com/getsentry/sentry-javascript/issues/12310)) - ref(profiling): unref timer ([#12340](https://togithub.com/getsentry/sentry-javascript/issues/12340)) ### [`v8.7.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#870) ##### Important Changes - **feat(react): Add TanStack Router integration ([#12095](https://togithub.com/getsentry/sentry-javascript/issues/12095))** This release adds instrumentation for TanStack router with a new `tanstackRouterBrowserTracingIntegration` in the `@sentry/react` SDK: ```javascript import * as Sentry from '@sentry/react'; import { createRouter } from '@tanstack/react-router'; const router = createRouter({ // Your router options... }); Sentry.init({ dsn: '___PUBLIC_DSN___', integrations: [Sentry.tanstackRouterBrowserTracingIntegration(router)], tracesSampleRate: 1.0, }); ``` ##### Other Changes - fix(nextjs): Do not hide `sourceMappingURL` comment on client when `nextConfig.productionBrowserSourceMaps: true` is set ([#12278](https://togithub.com/getsentry/sentry-javascript/issues/12278)) ### [`v8.6.0`](https://togithub.com/getsentry/sentry-javascript/blob/HEAD/CHANGELOG.md#860) ##### Important Changes - **feat(metrics): Add `timings` method to metrics ([#12226](https://togithub.com/getsentry/sentry-javascript/issues/12226))** This introduces a new method, `metrics.timing()`, which can be used in two ways: 1. With a numeric value, to simplify creating a distribution metric. This will default to `second` as unit: ```js Sentry.metrics.timing('myMetric', 100); ``` 2. With a callback, which will wrap the duration of the callback. This can accept a sync or async callback. It will create an inactive span around the callback and at the end emit a metric with the duration of the span in seconds: ```js const returnValue = Sentry.metrics.timing('myMetric', measureThisFunction); ``` - **feat(react): Add `Sentry.reactErrorHandler` ([#12147](https://togithub.com/getsentry/sentry-javascript/issues/12147))** This PR introduces `Sentry.reactErrorHandler`, which you can use in React 19 as follows: ```js import * as Sentry from '@sentry/react'; import { hydrateRoot } from 'react-dom/client'; ReactDOM.hydrateRoot( document.getElementById('root'),Configuration
📅 Schedule: Branch creation - "on the first day of the month" in timezone Asia/Tokyo, 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.
This PR has been generated by Mend Renovate. View repository job log here.