fix(deps): update sentry-javascript monorepo to v7.47.0 #3356
No reviewers
Labels
No Label
area/internal-code
changes requested
confirmed
dependencies
duplicate
good first issue
help wanted
hosting
invalid
kind/bug
kind/feature
question
wontfix
No Milestone
No project
No Assignees
4 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: vikunja/frontend#3356
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/sentry-javascript-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
7.46.0
->7.47.0
7.46.0
->7.47.0
Release Notes
getsentry/sentry-javascript
v7.47.0
Compare Source
Important Changes
This release adds a new API,
Sentry.captureUserFeedback
, to browser-side SDKs that allows you to send user feedback to Sentry without loading and opening Sentry's user feedback dialog. This allows you to obtain user feedback however and whenever you want to and simply send it to Sentry using the SDK.For instance, you can collect feedback, whenever convenient as shown in this example:
Note that feedback needs to be coupled to an event but as in the example above, you can just use
Sentry.captureMessage
to generate one.You could also collect feedback in a custom way if an error happens and use the SDK to send it along:
@sentry/tracing
exports (#7611)With this release, we officially deprecate all exports from the
@sentry/tracing
package, in favour of using them directly from the main SDK package. The@sentry/tracing
package will be removed in a future major release.Please take a look at the Migration docs for more details.
Additional Features and Fixes
fetch
(#7626)LocalVariables
integration on Node < v18 (#7748)Redirect
s as exceptions (#7731)handleErrorWithSentry
(#7674)Work in this release contributed by @de-don and @TrySound. Thank you for your contributions!
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.
This PR has been generated by Renovate Bot.
Hi renovate!
Thank you for creating a PR!
I've deployed the changes of this PR on a preview environment under this URL: https://3356-renovate-sentry-javascript-monor--vikunja-frontend-preview.netlify.app
You can use this url to view the changes live and test them out.
You will need to manually connect this to an api running somehwere. The easiest to use is https://try.vikunja.io/.
Have a nice day!
Because this deprecates @sentry/tracing it will make finshing and merging #1991 much more important (I already did the migration there.
Interesting: the new
captureUserFeedback
addition!@dpschen Should we merge this before #1991?
I guess its fine to merge. Didn't check the logs but I expect deprecation warnings. Should be fine.