Open greenkeeper[bot] opened 4 years ago
After pinning to 5.11.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
dependency
@sentry/node was updated from 5.11.2
to 5.12.0
.Your tests are still failing with this version. Compare changes
dependency
@sentry/node was updated from 5.12.0
to 5.12.1
.Your tests are still failing with this version. Compare changes
maxTransactionTimeout
= 0
there is no timeoutmaxTransactionTimeout
is always enforced on transaction eventsdependency
@sentry/node was updated from 5.12.1
to 5.12.2
.Your tests are still failing with this version. Compare changes
dependency
@sentry/node was updated from 5.12.2
to 5.12.3
.Your tests are still failing with this version. Compare changes
dependency
@sentry/node was updated from 5.12.3
to 5.12.4
.Your tests are passing again with this update. Explicitly upgrade to this version π
ParseRequest
typing (#2433)dependency
@sentry/node was updated from 5.12.4
to 5.12.5
.Your tests are passing again with this update. Explicitly upgrade to this version π
dependency
@sentry/node was updated from 5.13.0
to 5.13.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
options.autoPopAfter
parameter to pushActivity
to prevent never-ending spans (#2459)sentry_timestamp
header (#2458)timestampWithMs
(#2442)dependency
@sentry/node was updated from 5.13.0
to 5.13.1
.Your tests are passing again with this update. Explicitly upgrade to this version π
>= 6
dependency
@sentry/node was updated from 5.13.1
to 5.13.2
.Your tests are passing again with this update. Explicitly upgrade to this version π
discardBackgroundSpans
to discard background spans by defaultdependency
@sentry/node was updated from 5.13.2
to 5.14.0
.Your tests are passing again with this update. Explicitly upgrade to this version π
performance
browser API to provide better instrumentation (#2474)dependency
@sentry/node was updated from 5.14.0
to 5.14.1
.Your tests are still failing with this version. Compare changes
dependency
@sentry/node was updated from 5.14.1
to 5.14.2
.Your tests are still failing with this version. Compare changes
dependency
@sentry/node was updated from 5.14.2
to 5.15.0
.Your tests are still failing with this version. Compare changes
tracesSampleRate
(#2500)forceNoChild
parameter from hub.startSpan
(#2500)Span
internal, only use hub.startSpan
(#2500)dependency
@sentry/node was updated from 5.15.4
to 5.15.5
.Your tests are passing again with this update. Explicitly upgrade to this version π
dependency
@sentry/node was updated from 5.15.5
to 5.16.0
.Your tests are still failing with this version. Compare changes
If you are a @sentry/apm
and did manual instrumentation using hub.startSpan
please be aware of the changes we did to the API. The recommended entry point for manual instrumentation now is Sentry.startTransaction
and creating child Span by calling startChild
on it. We have internal workarounds in place so the old code should still work but will be removed in the future. If you are only using the Tracing
integration there is no need for action.
RequestAnimationFrame
with correct context (#2570)Sentry.startTransaction
and Transaction.startChild
(#2600)beforeSend
(#2600)captureException/captureMessage
(#2627)
The dependency @sentry/node was updated from
5.11.1
to5.11.2
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
@sentry/node is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- β **coverage/coveralls:** First build on greenkeeper/@sentry/node-5.11.2 at 33.508% ([Details](https://coveralls.io/builds/28401612)). - β **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/AtomicLoans/agent/builds/643364402?utm_source=github_status&utm_medium=notification)).Release Notes for 5.11.2
Tracing
maxTransactionTimeout
determines the max length of a transactionFAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donβt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: