Skip to content
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

meta: Update changelog for 7.47.0 #7758

Merged
merged 33 commits into from
Apr 5, 2023
Merged

meta: Update changelog for 7.47.0 #7758

merged 33 commits into from
Apr 5, 2023

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Apr 5, 2023

747 ✈️

github-actions bot and others added 30 commits March 30, 2023 14:02
[Gitflow] Merge master into develop
…ntry` (#7674)

Previously, our `handleErrorWithSentry` wrapper did nothing if users didn't provide a custom error handler as an argument. While IMO it's good that the error handler is an optional parameter, this swallowed errors and didn't log them to the console anymore. 

This patch fixes that by adding a default error handler which our wrapper invokes if no custom handler was provided. The client- and server default handlers log the error to the console, exactly like the default handlers by SvelteKit ([client](https://github.com/sveltejs/kit/blob/369e7d6851f543a40c947e033bfc4a9506fdc0a8/packages/kit/src/core/sync/write_client_manifest.js#LL127C2-L127C2), [server](https://github.com/sveltejs/kit/blob/369e7d6851f543a40c947e033bfc4a9506fdc0a8/packages/kit/src/runtime/server/index.js#L43)).
As pointed out here: #7705 we can replace this with core functionality.
Update function `getParameterizedRouteFromSnapshot` to handle routes with empty paths.

Fixes #7681
Co-authored-by: Abhijeet Prasad <devabhiprasad@gmail.com>
Bumps [actions/stale](https://github.com/actions/stale) from 7.0.0 to 8.0.0.
- [Release notes](https://github.com/actions/stale/releases)
- [Changelog](https://github.com/actions/stale/blob/main/CHANGELOG.md)
- [Commits](actions/stale@6f05e42...1160a22)

---
updated-dependencies:
- dependency-name: actions/stale
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
As outlined in the [SvelteKit docs](https://kit.svelte.dev/docs/load#redirects), users can `throw redirect(300, 'route/to/redirect')` in `load` functions. We don't want to capture these as errors and send them to Sentry.
Bumps [@sveltejs/kit](https://github.com/sveltejs/kit/tree/HEAD/packages/kit) from 1.11.0 to 1.15.1.
- [Release notes](https://github.com/sveltejs/kit/releases)
- [Changelog](https://github.com/sveltejs/kit/blob/master/packages/kit/CHANGELOG.md)
- [Commits](https://github.com/sveltejs/kit/commits/@sveltejs/kit@1.15.1/packages/kit)

---
updated-dependencies:
- dependency-name: "@sveltejs/kit"
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
In #7667 we missed that our `urlToOptions` helper function is actually called to normalize request options that are then passed to the actual http client. Meaning, we shouldn't have redacted the authority in this function but at a later time when we extract the sanitized version (`extractUrl`). This PR changes the redaction location accordingly and hence fixes requests with authority not being sent properly. 

Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
…7626)

Add partial instrumentation to the client-side `fetch` passed to the universal `load` functions. It enables distributed traces of fetch calls happening **inside** a `load` function. 

Limitation: `fetch` requests made by SvelteKit (e.g. to call server-only load functions) are **not** touched by this instrumentation because we cannot access the Kit-internal fetch function at this time
Fix the report dialog being opened for events that are dropped. Leverage SDK lifecycle hooks (`afterSendEvent`) to open the dialog if hooks are available. Keep the current behaviour as a fallback if hooks are not available.
Add new API `captureUserFeedback` to Browser SDKs, allowing Sentry users to send feedback programmatically without opening and using the feedback dialog.

Co-authored-by: Luca Forstner <luca.forstner@sentry.io>
@Lms24 Lms24 requested review from a team, mydea, AbhiPrasad and lforst and removed request for a team April 5, 2023 13:21
@Lms24 Lms24 marked this pull request as ready for review April 5, 2023 13:30
@Lms24 Lms24 changed the base branch from develop to master April 5, 2023 13:30
@Lms24 Lms24 merged commit f4861f8 into master Apr 5, 2023
22 checks passed
@Lms24 Lms24 deleted the prepare-release/7.47.0 branch April 5, 2023 13:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants