search

ViMaSter / gdqreminder-mobile

Android app using Vue + Capacitor to keep track of GamesDoneQuick events
https://play.google.com/store/apps/details?id=ke.mahn.gdqreminder
GNU General Public License v3.0
4 stars 0 forks source link

chore(deps): bump the sentry group with 2 updates #1251

Closed dependabot[bot] closed 2 months ago

dependabot[bot] commented 2 months ago

Bumps the sentry group with 2 updates: @sentry/vue and @sentry/vite-plugin.

Updates @sentry/vue from 8.9.2 to 8.16.0

Release notes

Sourced from @​sentry/vue's releases.

8.16.0

Important Changes

  • feat(nextjs): Use spans generated by Next.js for App Router (#12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have a root span, and more importantly, if you had data stream to the client, its duration was not captured because the server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with server component spans being descendants of that transaction. This means you will get more data that is also more accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge runtime), and you will instead receive transactions for your App Router SSR requests that look like GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

  • - feat(nestjs): Add nest cron monitoring support (#12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@nestjs/schedule';
import { SentryCron, MonitorConfig } from '@sentry/nestjs';
import type { MonitorConfig } from '@sentry/types';

const monitorConfig: MonitorConfig = {

schedule: {

type: 'crontab',

value: '* * * * *',

},

checkinMargin: 2, // In minutes. Optional.

maxRuntime: 10, // In minutes. Optional.

timezone: 'America/Los_Angeles', // Optional.

};


export class MyCronService {

@​Cron('* * * * *')

@​SentryCron('my-monitor-slug', monitorConfig)

handleCron() {

// Your cron job logic here

}

}

... (truncated)

Changelog

Sourced from @​sentry/vue's changelog.

8.16.0

Important Changes

  • feat(nextjs): Use spans generated by Next.js for App Router (#12729)

Previously, the @sentry/nextjs SDK automatically recorded spans in the form of transactions for each of your top-level server components (pages, layouts, ...). This approach had a few drawbacks, the main ones being that traces didn't have a root span, and more importantly, if you had data stream to the client, its duration was not captured because the server component spans had finished before the data could finish streaming.

With this release, we will capture the duration of App Router requests in their entirety as a single transaction with server component spans being descendants of that transaction. This means you will get more data that is also more accurate. Note that this does not apply to the Edge runtime. For the Edge runtime, the SDK will emit transactions as it has before.

Generally speaking, this change means that you will see less transactions and more spans in Sentry. You will no longer receive server component transactions like Page Server Component (/path/to/route) (unless using the Edge runtime), and you will instead receive transactions for your App Router SSR requests that look like GET /path/to/route.

If you are on Sentry SaaS, this may have an effect on your quota consumption: Less transactions, more spans.

  • - feat(nestjs): Add nest cron monitoring support (#12781)

The @sentry/nestjs SDK now includes a @SentryCron decorator that can be used to augment the native NestJS @Cron decorator to send check-ins to Sentry before and after each cron job run:

import { Cron } from '@nestjs/schedule';
import { SentryCron, MonitorConfig } from '@sentry/nestjs';
import type { MonitorConfig } from '@sentry/types';

const monitorConfig: MonitorConfig = {

schedule: {

type: 'crontab',

value: '* * * * *',

},

checkinMargin: 2, // In minutes. Optional.

maxRuntime: 10, // In minutes. Optional.

timezone: 'America/Los_Angeles', // Optional.

};


export class MyCronService {

@​Cron('* * * * *')

@​SentryCron('my-monitor-slug', monitorConfig)

handleCron() {

// Your cron job logic here

}

}

</tr></table>

... (truncated)

Commits


Updates @sentry/vite-plugin from 2.18.0 to 2.20.1

Release notes

Sourced from @​sentry/vite-plugin's releases.

2.20.1

  • feat(telemetry): Collect whether applicationKey is set (#559)
  • fix: Wait for tasks depending on sourcemaps before deleting (#557)

2.20.0

  • feat: Export esbuild plugin as default (#555)

2.19.0

  • feat: Don't use word "error" in log message about telemetry (#548)
  • feat(core): Detect releases from more providers (#549)
  • fix: Always delete files when sourcemaps.filesToDeleteAfterUpload is set (#547)
  • fix(vite): Fix environment variable loading issue for Windows (#545)

Work in this release contributed by @​Rassilion, and @​mateusz-daniluk-xtb. Thank you for your contributions!

Changelog

Sourced from @​sentry/vite-plugin's changelog.

2.20.1

  • feat(telemetry): Collect whether applicationKey is set (#559)
  • fix: Wait for tasks depending on sourcemaps before deleting (#557)

2.20.0

  • feat: Export esbuild plugin as default (#555)

2.19.0

  • feat: Don't use word "error" in log message about telemetry (#548)
  • feat(core): Detect releases from more providers (#549)
  • fix: Always delete files when sourcemaps.filesToDeleteAfterUpload is set (#547)
  • fix(vite): Fix environment variable loading issue for Windows (#545)

Work in this release contributed by @​Rassilion, and @​mateusz-daniluk-xtb. Thank you for your contributions!

Commits
  • efc8e2e release: 2.20.1
  • 0339fd6 meta: Update changelog for 2.20.1
  • 473e371 feat(telemetry): Collect whether applicationKey is set (#559)
  • 75ca15e fix: Wait for tasks depending on sourcemaps before deleting (#557)
  • 62de37e Merge branch 'release/2.20.0'
  • 3d3da7a release: 2.20.0
  • 9982c89 meta: Update changelog for 2.20.0
  • 604077b feat: Export esbuild plugin as default (#555)
  • 4451157 Merge branch 'release/2.19.0'
  • 50bf988 release: 2.19.0
  • Additional commits viewable in compare view


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 show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions