-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(deps): update dependency @sentry/node to v7 #977
Merged
bodinsamuel
merged 1 commit into
chore/renovateBaseBranch
from
renovate/major-7-sentry-javascript-monorepo
Aug 2, 2022
Merged
fix(deps): update dependency @sentry/node to v7 #977
bodinsamuel
merged 1 commit into
chore/renovateBaseBranch
from
renovate/major-7-sentry-javascript-monorepo
Aug 2, 2022
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
7 times, most recently
from
June 11, 2022 20:43
d59a347
to
7e30ca0
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
from
June 17, 2022 14:22
7e30ca0
to
b2d1716
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
12 times, most recently
from
June 26, 2022 02:42
ee19c5e
to
b51804c
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
4 times, most recently
from
July 8, 2022 14:33
8409391
to
30e0883
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
6 times, most recently
from
July 10, 2022 23:25
17bcd01
to
f9d24bd
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
6 times, most recently
from
July 18, 2022 05:05
ab55a8b
to
d5166af
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
7 times, most recently
from
July 30, 2022 18:30
9a3f6e8
to
3f59559
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
2 times, most recently
from
August 1, 2022 02:09
d643d4c
to
1197782
Compare
renovate
bot
force-pushed
the
renovate/major-7-sentry-javascript-monorepo
branch
from
August 1, 2022 02:16
1197782
to
8908088
Compare
renovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7
fix(deps): update dependency @sentry/node to v7 - autoclosed
Aug 2, 2022
renovate
bot
changed the title
fix(deps): update dependency @sentry/node to v7 - autoclosed
fix(deps): update dependency @sentry/node to v7
Aug 2, 2022
bodinsamuel
pushed a commit
that referenced
this pull request
Aug 2, 2022
* chore: automatic empty commit * chore(deps): update dependency jest-junit to v14 (#997) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * fix(deps): update dependency @sentry/node to v7 (#977) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency husky to v8 (#964) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency eslint-plugin-jest to v26 (#861) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): update dependency lint-staged to v13 (#976) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> * chore(deps): lock file maintenance (#971) Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: Samuel Bodin <samuel.bodin@algolia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
6.19.7
->7.8.0
Release Notes
getsentry/sentry-javascript
v7.8.0
Compare Source
This release adds the
transpileClientSDK
flag to the Next.JS SDK Webpack config. This option makes WebPack transpile the SDK code to the same transpilation level as the user code. By specifying this option, the Next.JS SDK works in older browsers that do not support ES6 or ES6+ (e.g. object spread) features.captureUnderscoreErrorException
argument type (#5463)eval
when checking forsentry-cli
binary (#5447)isBuild
into an exported function (#5444)_error.js
(#5378)RewriteFrames
helper value (#5445)Work in this release contributed by @mitchheddles. Thank you for your contribution!
v7.7.0
Compare Source
sentry_client
to auth headers (#5413)documentRequest
function name. (#5404)ok
responses as errors. (#5405)v7.6.0
Compare Source
This release adds the
source
field to all outgoing transactions.See the tracking GH issue for more details.
This release also re-enables lambda layer releases for the Node Serverless SDK.
Work in this release contributed by @moishinetzer. Thank you for your contribution!
v7.5.1
Compare Source
This release removes the
user_id
and thetransaction
field from the dynamic sampling context data that is attached to outgoing requests as well as sent to Relay.v7.5.0
Compare Source
This release adds the
sendDefaultPii
flag to theSentry.init
options.When using performance monitoring capabilities of the SDK, it controls whether user IDs (set via
Sentry.setUser
) are propagated in thebaggage
header of outgoing HTTP requests.This flag is set to
false
per default, and acts as an opt-in mechanism for sending potentially sensitive data.If you want to attach user IDs to Sentry transactions and traces, set this flag to
true
but keep in mind that this is potentially sensitive information.user_id
to DSC ifsendDefaultPii
istrue
(#5344)Work in this release contributed by @jkcorrea and @nfelger. Thank you for your contributions!
v7.4.1
Compare Source
This release includes the first published version of
@sentry/remix
.v7.4.0
Compare Source
This release contains the alpha version of
@sentry/remix
, our newest JavaScript SDK! For details on how to useit, please see the README and the tracking GitHub issue.
Attention: Due to an oversight, the
@sentry/remix
package is only published as part of the7.4.1
release.Work in this release contributed by @MichaelDeBoey. Thank you for your contribution!
Special thank you to @jacob-ebey for pointing us in the right direction while we were working on the Remix SDK:
https://github.com/jacob-ebey/remix-sentry.
v7.3.1
Compare Source
Work in this release contributed by @MasterOdin. Thank you for your contribution!
v7.3.0
Compare Source
_error.js
(#5259)ParseRequestOptions
to be passed to request handler (#5287)Work in this release contributed by @Arinono. Thank you for your contribution!
v7.2.0
Compare Source
showReportDialog
from NextJS SDK (#5242)@sentry/utils
(#5257)Work in this release contributed by @Arinono and @slaesh. Thank you for your contributions!
v7.1.1
Compare Source
v7.1.0
Compare Source
http
transport (#5209)dropUndefinedKeys
(#5201)debug.min
bundle variant config (#5192)handlers
module (#5190)v7.0.0
Compare Source
Version 7 of the Sentry JavaScript SDK brings a variety of features and fixes including bundle size and performance improvements, brand new integrations, support for the attachments API, and key bug fixes.
This release does not change or remove any top level public API methods (
captureException
,captureMessage
), and only requires changes to certain configuration options or custom clients/integrations/transports.Note: The v7 version of the JavaScript SDK requires a self-hosted version of Sentry 20.6.0 or higher. If you are using a version of self-hosted Sentry (aka onpremise) older than
20.6.0
then you will need to upgrade.For detailed overview of all the changes, please see our v7 migration guide.
Breaking Changes
If you are a regular consumer of the Sentry JavaScript SDK you only need to focus on the general items. The internal breaking changes are aimed at libraries that build on top of and extend the JavaScript SDK (like
@sentry/electron
or@sentry/react-native
).General
bundle.min.js
to ES6 instead of ES5. ES5 bundles are still available atbundle.es5.min.js
. (#4958)Severity
enum for bundle size reasons. Please use string literals instead. (#4926)critical
Severity level. (#5032)whitelistUrls
andblacklistUrls
have been renamed toallowUrls
anddenyUrls
in theSentry.init()
options. (#4850)BaseClient
and it's child classes now requiretransport
,stackParser
, andintegrations
to be explicitly passed in. This was done to improve tree-shakability. (#4927)@sentry/*
npm packages. See details in our migration docs.. (#4900) (#4901)Transport
API. This means custom transports will have to be adjusted accordingly..baggage
HTTP header alongsidesentry-trace
header to propogate additional tracing related information.. (#5133)registerRequestInstrumentation
export toinstrumentOutgoingRequests
in@sentry/tracing
. (#4859)UserAgent
integration toHttpContext
. (#5027)BrowserTracing
integration'smaxTransactionDuration
option withfinalTimeout
option in the@sentry/tracing
package and resetidleTimeout
based on activities count. This should improve accuracy of web-vitals like LCP by 20-30%. (#5044)@sentry/angular
to be compiled by the angular compiler. (#4641)@sentry/minimal
package in favour of using@sentry/hub
. (#4971)ignoreSentryErrors
option from AWS lambda SDK. Errors originating from the SDK will now always be caught internally. (#4994)Integrations.BrowserTracing
export from@sentry/nextjs
. Please importBrowserTracing
from@sentry/nextjs
directly.id
property fromBrowserTracing
integration.SDK_NAME
export from@sentry/browser
,@sentry/node
,@sentry/tracing
and@sentry/vue
packages. (#5040)Angular
,Ember
, andVue
integrations from@sentry/integrations
in favour of the explicit framework packages:@sentry/angular
,@sentry/ember
, and@sentry/vue
. (#4893)Status
,RequestSessionStatus
, andSessionStatus
.. Deprecated enumsSpanStatus
andSeverity
. This was done to save on bundle size. (#4891) (#4889) (#4890)@sentry/apm
package. (#4845)user
field from DSN interface.publicKey
should be used instead. (#4864)getActiveDomain
method andDomainAsCarrier
type from@sentry/hub
. (#4858)eventStatusFromHttpCode
to save on bundle size.event.stacktrace
field. (#4885)showReportDialog
method onBrowserClient
(#4973)startSpan
andchild
methods (#4849)frameContextLines
options (#4884)Sentry
from window in the Gatsby SDK (#4857)Internal
API
class from@sentry/core
.. (#4848)Session
class to use a more functional approach.. (#5054)Backend
class in favour of moving functionality into theClient
class (for more details, see #4911 and #4919).@sentry-internal/typescript
(#4940)_invokeClient
function from@sentry/hub
(#4972)@sentry/utils
(#5066)Other Changes
Features
name
field toEventProcessor
(#4932)setMeasurement
public API (#4933)Fixes
addEventListener
instrumentation (#5147)gcpfunction
(#5097)querySelector
when not available (#5160)dropUndefinedKeys
(#5163)Misc
Configuration
📅 Schedule: Branch creation - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, 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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.