fossasia / open-event-next

Open Event Frontend "Next Version" with Vue.js
Apache License 2.0
1.52k stars 101 forks source link

chore(deps): Bump @sentry/node from 6.18.1 to 7.55.0 #791

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps @sentry/node from 6.18.1 to 7.55.0.

Release notes

Sourced from @​sentry/node's releases.

7.55.0

  • feat(replay): Capture slow clicks (GA) (#8298)
  • feat(replay): Improve types for replay recording events (#8224)
  • fix(nextjs): Strip query params from transaction names of navigations to unknown routes (#8278)
  • fix(replay): Ignore max session life for buffered sessions (#8258)
  • fix(sveltekit): Export captureCheckIn (#8313)
  • ref(svelte): Add Svelte 4 as a peer dependency (#8280)

Bundle size 📦

Path Size
@​sentry/browser - ES5 CDN Bundle (gzipped + minified) 21.12 KB
@​sentry/browser - ES5 CDN Bundle (minified) 65.86 KB
@​sentry/browser - ES6 CDN Bundle (gzipped + minified) 19.65 KB
@​sentry/browser - ES6 CDN Bundle (minified) 58.34 KB
@​sentry/browser - Webpack (gzipped + minified) 21.28 KB
@​sentry/browser - Webpack (minified) 69.26 KB
@​sentry/react - Webpack (gzipped + minified) 21.31 KB
@​sentry/nextjs Client - Webpack (gzipped + minified) 49.23 KB
@​sentry/browser + @​sentry/tracing - ES5 CDN Bundle (gzipped + minified) 28.74 KB
@​sentry/browser + @​sentry/tracing - ES6 CDN Bundle (gzipped + minified) 26.98 KB
@​sentry/replay ES6 CDN Bundle (gzipped + minified) 48.68 KB
@​sentry/replay - Webpack (gzipped + minified) 42.26 KB
@​sentry/browser + @​sentry/tracing + @​sentry/replay - ES6 CDN Bundle (gzipped + minified) 67.63 KB
@​sentry/browser + @​sentry/replay - ES6 CDN Bundle (gzipped + minified) 60.54 KB

7.54.0

Important Changes

  • feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

    All SDKs now filter out health check transactions by default. These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names. We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. These filters are implemented as default values for the top level ignoreTransactions option.

    You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:

    Sentry.init({
      //...
      integrations: [new InboundFilters({ disableTransactionDefaults: true })],
    })
    
  • feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

    The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

    A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers.

... (truncated)

Changelog

Sourced from @​sentry/node's changelog.

7.55.0

  • feat(replay): Capture slow clicks (GA) (#8298)
  • feat(replay): Improve types for replay recording events (#8224)
  • fix(nextjs): Strip query params from transaction names of navigations to unknown routes (#8278)
  • fix(replay): Ignore max session life for buffered sessions (#8258)
  • fix(sveltekit): Export captureCheckIn (#8313)
  • ref(svelte): Add Svelte 4 as a peer dependency (#8280)

7.54.0

Important Changes

  • feat(core): Add default entries to ignoreTransactions for Healthchecks #8191

    All SDKs now filter out health check transactions by default. These are transactions where the transaction name matches typical API health check calls, such as /^.*healthy.*$/ or /^. *heartbeat.*$/. Take a look at this list to learn which regexes we currently use to match transaction names. We believe that these transactions do not provide value in most cases and we want to save you some of your quota by filtering them out by default. These filters are implemented as default values for the top level ignoreTransactions option.

    You can disable this filtering by manually specifiying the InboundFilters integration and setting the disableTransactionDefaults option:

    Sentry.init({
      //...
      integrations: [new InboundFilters({ disableTransactionDefaults: true })],
    })
    
  • feat(replay): Add mutationBreadcrumbLimit and mutationLimit to Replay Options (#8228)

    The previously experimental options mutationBreadcumbLimit and mutationLimit have been promoted to regular Replay integration options.

    A high number of DOM mutations (in a single event loop) can cause performance regressions in end-users' browsers. Use mutationBreadcrumbLimit to send a breadcrumb along with your recording if the mutation limit was reached. Use mutationLimit to stop recording if the mutation limit was reached.

  • feat(sveltekit): Add source maps support for Vercel (lambda) (#8256)

    • feat(sveltekit): Auto-detect SvelteKit adapters (#8193)

    The SvelteKit SDK can now be used if you deploy your SvelteKit app to Vercel. By default, the SDK's Vite plugin will detect the used adapter and adjust the source map uploading config as necessary. If you want to override the default adapter detection, you can specify the adapter option in the sentrySvelteKit options:

    // vite.config.js
    export default defineConfig({
      plugins: [
        sentrySvelteKit({
          adapter: 'vercel',
        }),
    

... (truncated)

Commits
  • b07238b release: 7.55.0
  • 0f3f211 Merge pull request #8318 from getsentry/prepare-release/7.55.0
  • f81981d meta(changelog): Update changelog for 7.55.0
  • 435847d fix(sveltekit): Export captureCheckIn (#8313)
  • 8934ccc test(replay): Fix test (#8310)
  • b877c10 chore: Add missing fields into Replay NetworkRequestData type (#8284)
  • 1b37517 feat(replay): Capture slow clicks (GA) (#8298)
  • 8ffde2a fix(replay): Ignore max session life for buffered sessions (#8258)
  • 62e7265 chore(deps-dev): bump vite from 4.0.0 to 4.0.5
  • bca567e test(e2e): Disable concurrent tests for canary tests (#8287)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
vercel[bot] commented 1 year ago

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

Name Status Preview Comments Updated (UTC)
open-event-next ❌ Failed (Inspect) Jun 13, 2023 10:06pm
dependabot[bot] commented 1 year ago

Superseded by #792.