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.54.0 #8271

Merged
merged 20 commits into from
Jun 1, 2023
Merged

meta: Update changelog for 7.54.0 #8271

merged 20 commits into from
Jun 1, 2023

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented Jun 1, 2023

github-actions bot and others added 20 commits May 24, 2023 16:21
[Gitflow] Merge master into develop
These debug statements are not really providing value, removing them...
…est Handlers (#8215)

Stop sending thrown redirects and 4xx Http errors to
Sentry. This change is identical to #7731 which introduced these filters
to `load` functions.
This updates custom breadcrumb handling to be throttled to max. 300
breadcrumbs/5s.

If we exceed this amount of breadcrumbs, we drop any further breadcrumbs
and instead add a single breadcrumb with `category: 'replay.throttled'`,
which the UI can use to indicate that _something_ was dropped.

Closes #8072

---------

Co-authored-by: Billy Vong <billyvg@users.noreply.github.com>
`key` _should_ always be there, but let's guard against this as it seems
it may be undefined.

Fixes #8237
1. Do not create an issue when manually running canary tests
2. Update existing issue instead of creating a new one every time
3. Update issue name so we see which canary test is failing
These tests seem to only flake on firefox?
Bump `magicast` to the latest version, 0.2.8, which fixes auto instrumentation of files with `satisfies` keywords.
…arameters (#8213)

Fix transaction names having query params or fragments attached when request URLs without any route parameters were encountered under [certain conditions](#8213 (comment)), 

Fixes #6586
…tes (#8201)

Adds a `handleUnknownRoutes` option to the `sentryHandle` server
request handler. The option defaults to `false` which will effectively
reduce noise, such as random bot requests. Previously such requests
would yield e.g. `GET null` transactions because they could not be
matched to an existing route by the framework. See #8199
First step for Vercel support: Detecting the used SvelteKit adapter.

(This currently does nothing other than detecting the adapter; next step
is to configure the source maps plugin correctly for the respective
adapters)

ref #8085
…blobs (#8263)

Try-catch the URL creation to avoid throwing an error if a funky URL is
encountered.

fixes #8259 

This will not fix symbolication for blob/binary WASM modules that aren't
directly fetched but at least we don't error anymore
…o regular feature (#8228)

Instead of taking a fullsnapshot when `mutationLimit` is reached, lets
be aggressive and stop the replay to ensure end-users are not negatively
affected performance wise.

The default for showing a breadcrumb is at 750 mutations, and the
default limit to stop recording is 10000 mutations.

Closes #8002
Adjust our automatic source maps upload setup in the SvelteKit
SDK to support SvelteKit apps deployed to Vercel. This will only work
for Lambda functions/Node runtime; not for the Vercel Edge runtime.

This required a few changes in our custom vite plugin as well as on the
server side of the SDK:

* Based on the used adapter (manually set or detected via #8193) and the
`svelte.config.js` we determine the output directory where the generated
JS emitted to.
* The determined output directory is injected into the global object on
the server side
* When an error occurs on the server side, we strip the absolute
filename of each stack frame so that the relative path of the
server-side code within the output directory is left.
* We also use the determined output directory to build the correct
`include` entries for the source map upload plugin.

With this change, source maps upload should work for auto and Vercel
adapters, as well as for the Node adapter.
As for the Node adapter, the stackframe rewrite behaviour was also
changed but it is now more in line with all supported adapters.
Ignore health check transactions by default.
Provide option to enable them via `InboundFilters` option `disableTransactionDefaults`.

Ref: getsentry/team-webplatform-meta#70
…ion (#8268)

Ensure that the loadContext created in the remix server is passed
through to `app/entry.server.ts` in the document request handler.

Fixes issue #8265.
We are logging a warning when any of the required hooks / functions to
Remix Browser SDK are not available in the Root component.

This Root component is also rendered on server-side where we don't have
access to those functions. And as we're not creating pageload /
navigation transactions there, those functions are not required anyway.

So this PR prevents that warning to be logged on server-side which is
misleading.
@Lms24 Lms24 changed the base branch from develop to master June 1, 2023 12:16
@Lms24 Lms24 requested a review from mydea June 1, 2023 12:17
@Lms24 Lms24 merged commit 77d4204 into master Jun 1, 2023
21 checks passed
@Lms24 Lms24 deleted the prepare-release/7.54.0 branch June 1, 2023 12:28
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

8 participants