search

CreepPork / Apollo

Discord bot that allows to get status updates on your Arma 3 server.
MIT License
16 stars 9 forks source link

Bump @sentry/node from 5.6.2 to 5.13.1 #104

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps @sentry/node from 5.6.2 to 5.13.1.

Release notes

Sourced from @sentry/node's releases.

5.13.1

  • [node] fix: Restore engines back to >= 6

5.13.0

  • [apm] feat: Add options.autoPopAfter parameter to pushActivity to prevent never-ending spans (#2459)
  • [apm] fix: Use monotonic clock to compute durations (#2441)
  • [core] ref: Remove unused sentry_timestamp header (#2458)
  • [node] ref: Drop Node v6, add Node v12 to test matrix, move all scripts to Node v12 (#2455)
  • [utils] ref: Prevent instantiating unnecessary Date objects in timestampWithMs (#2442)
  • [browser] fix: Mark transactions as event.transaction in breadcrumbs correctly

5.12.5

  • [browser] ref: Mark transactions as event.transaction in breadcrumbs (#2450)
  • [node] fix: Dont overwrite servername in requestHandler (#2449)
  • [utils] ref: Move creation of iframe into try/catch in fetch support check (#2447)

5.12.4

  • [browser] ref: Rework XHR wrapping logic to make sure it always triggers
  • [browser] fix: Handle PromiseRejectionEvent-like CustomEvents (#2429)
  • [core] ref: Notify user when event failed to deliver because of digestion pipeline issue (#2416)
  • [node] fix: Improve incorrect ParseRequest typing (#2433)
  • [apm] fix: Remove auto unknown_error transaction status (#2440)
  • [apm] fix: Properly remove undefined keys from apm payload (#2414)

5.12.3

  • [apm] fix: Remove undefined keys from trace.context

5.12.2

  • [apm] ref: Check if Tracing integration is enabled before dropping transaction

5.12.1

  • [apm] ref: If maxTransactionTimeout = 0 there is no timeout
  • [apm] fix: Make sure that the maxTransactionTimeout is always enforced on transaction events
  • [browser] fix: Support for Hermes stacktraces

5.12.0

  • [core] feat: Provide normalizeDepth option and sensible default for scope methods (#2404)
  • [browser] fix: Export EventHint type (#2407)

5.11.2

  • [apm] fix: Add new option to Tracing maxTransactionTimeout determines the max length of a transaction
  • [hub] ref: Always also set transaction name on the top span in the scope
  • [core] fix: Use event_id from hint given by top-level hub calls

5.11.1

  • [apm] feat: Add build bundle including @sentry/browser + @sentry/apm
  • [utils] ref: Extract adding source context incl. tests

5.11.0

  • [apm] fix: Always attach contexts.trace to finished transaction (#2353)
... (truncated)
Changelog

Sourced from @sentry/node's changelog.

5.13.1

  • [node] fix: Restore engines back to >= 6

5.13.0

  • [apm] feat: Add options.autoPopAfter parameter to pushActivity to prevent never-ending spans (#2459)
  • [apm] fix: Use monotonic clock to compute durations (#2441)
  • [core] ref: Remove unused sentry_timestamp header (#2458)
  • [node] ref: Drop Node v6, add Node v12 to test matrix, move all scripts to Node v12 (#2455)
  • [utils] ref: Prevent instantiating unnecessary Date objects in timestampWithMs (#2442)
  • [browser] fix: Mark transactions as event.transaction in breadcrumbs correctly

5.12.5

  • [browser] ref: Mark transactions as event.transaction in breadcrumbs (#2450)
  • [node] fix: Dont overwrite servername in requestHandler (#2449)
  • [utils] ref: Move creation of iframe into try/catch in fetch support check (#2447)

5.12.4

  • [browser] ref: Rework XHR wrapping logic to make sure it always triggers (#2438)
  • [browser] fix: Handle PromiseRejectionEvent-like CustomEvents (#2429)
  • [core] ref: Notify user when event failed to deliver because of digestion pipeline issue (#2416)
  • [node] fix: Improve incorrect ParseRequest typing (#2433)
  • [apm] fix: Remove auto unknown_error transaction status (#2440)
  • [apm] fix: Properly remove undefined keys from apm payload (#2414)

5.12.3

  • [apm] fix: Remove undefined keys from trace.context (#2413)

5.12.2

  • [apm] ref: Check if Tracing integration is enabled before dropping transaction

5.12.1

  • [apm] ref: If maxTransactionTimeout = 0 there is no timeout (#2410)
  • [apm] fix: Make sure that the maxTransactionTimeout is always enforced on transaction events (#2410)
  • [browser] fix: Support for Hermes stacktraces (#2406)

5.12.0

  • [core] feat: Provide normalizeDepth option and sensible default for scope methods (#2404)
  • [browser] fix: Export EventHint type (#2407)

5.11.2

  • [apm] fix: Add new option to Tracing maxTransactionTimeout determines the max length of a transaction (#2399)
... (truncated)
Commits
  • 0ceba79 release: 5.13.1
  • c45b649 meta: 5.13.1 changelog
  • 5b78cbc ref: Restore node 6 support due to yarn engine checks, add performance.now fa...
  • 73c28c5 Merge release/5.13.0 into master
  • 5de0e3b release: 5.13.0
  • 0d8c054 meta: 5.13.0 changelog
  • bc5ee8f feat: Add autoPop parameter and add debug logs (#2459)
  • 6e1f442 ref: Create crossPlatformPerformance layer with better typings and fallback f...
  • 13d8398 fix: Use monotonic clock to compute durations (#2441)
  • 2e11882 ref: Remove unused sentry_timestamp header (#2458)
  • 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) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)
dependabot-preview[bot] commented 4 years ago

Superseded by #112.