meta: Update Changelog for 8.26.0 #13351
Merged
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
[Gitflow] Merge master into develop
Enable long animation frames by default. If long animation frames are not supported by the browser, Sentry will fallback to using long tasks where enabled.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #13296 --------- Co-authored-by: andreiborza <168741329+andreiborza@users.noreply.github.com> Co-authored-by: Andrei Borza <andrei.borza@sentry.io>
This PR streamlines and fixes some timing/cleanup issues we had in integration tests, which sometimes lead to issues. One problem was introduced here: #13253 This change lead to the server being shut down (because `done` is called) before the HTTP requests are finished, leading to error logs. Another problem was that in some cases we had leaking processes, where we did not properly close servers we started - this was everywhere we used `createTestServer`. I also moved some code from the node-integration-tests package to the remix package, that was only used there (and not properly depended/imported on). For future debugging, this was shown by running tests with `--detectOpenHandles`.
Making sure tracing without performance works. ref (SvelteKit): #13231
…al (#13282) If the kind of a http span is neither client nor server, it implies it is most likely being started with `startSpan()` manually, in which case we rather not want to overwrite the name.
#13306) In Astro middleware, we're not allowed to access the `request.headers` object if the incoming request is for a statically generated/prerendered route. Since we accessed these headers previously, users would get a warning as reported multiple times and tracked in #13116. This patch fixes that by checking for static vs dynamic route
Node 22 brings with it: - `node --run` to run scripts (fast) - stable `node --watch` - `glob` in `node:fs` which should allow us to remove a couple of our dependencies and clean up our scripts.
) Makes it possible to add bundle size optimizations along with source maps options to the SvelteKit plugin options like this: ```js sourceMapsUploadOptions: { authToken: 'token', org: 'org', project: 'project', }, bundleSizeOptimizations: { excludePerformanceMonitoring: true, excludeTracing: true }, ``` A bit of refactoring was done as well in the PR: - exported all types necessary for the plugin from `./types` - create a function `generateVitePluginOptions` which merges all SvelteKit plugin options correctly to create the Vite Plugin options (+ tests for this function) part of #13011
Noticed that we still called this out as alpha, even though it is not.
builds on top of #13306, found while working on #13116 This PR ensures that we correctly extract the request data in our Astro middleware. Previously we didn't convert the `request.headers` object into a `Record<string, string>` but simply passed a `Headers` instance. This caused problems with the `requestDataIntegration` which doesn't handle the instance correctly.
Adds a browser-side integration for sending events and Sentry requests to Spotlight. The integration is not enabled by default but can be added by users if they want to explicitly send browser SDK events to spotlight. This is especially helpful if people use spotlight in the electron app or a standalone browser window instead of the overlay. --- Co-authored-by: Burak Yigit Kaya <bkaya21@bloomberg.net>
Setting the transaction name to display the API route where the error happened: 
…13281) Add an Otel-specific implementation of `getTraceData` and add the `getTraceData` function to the `AsyncContextStrategy` interface. This allows us to dynamically choose either the default implementation (which works correctly for browser/non-POTEL SDKs) and the Otel-specific version.
Removes the old `logInfo` function and replaces it with a new
replay-specific
logger. Configuration is done when the replay integration is first
initialized
to avoid needing to pass around configuration options. This also means
that we cannot select individual log statements to be added as
breadcrumbs with
`traceInternals` options.
This also adds a `logger.exception` that wraps `captureException`.
Note that only the following logging levels are supported:
* `info`
* `log`
* `warn`
* `error`
With two additions:
* `exception`
* `infoTick` (needs a better name) - same as `info` but adds the
breadcrumb in the next tick due to some pre-existing race conditions
There is one method to configure the logger:
* `setConfig({ traceInternals, captureExceptions })`
Add e2e test app for `@sentry/browser` package, testing - error - pageload span - navigation span --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Add `safari-web-extension:` to the list of allowed extension protocols. This chage should allow sentry/browser to work in safari browser extensions.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #13125 --- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #13209 --- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Add an experimental feature to `browserTracingIntegration` to no longer tie CLS reporting to the ongoing pageload span but instead send a standalone CLS span similarly to how we report INP. The big advantage of this reporting strategy is that layout shifts happening after the pageload idle span ended, will also get reported. This should give users more accurate CLS values in the web vitals performance insights module.
Adds explicit imports in case `autoImport` is disabled (Nuxt docs [here](https://nuxt.com/docs/guide/concepts/auto-imports#disabling-auto-imports)). Disabled `autoImport` in the E2E test to verify. fixes #13302
…equestInfo.path` change in Next.js canary (#13344)
…a status and clarify usage recommendations (#13329)
Lms24
force-pushed
the
prepare-release/8.26.0
branch
from
5b19903
to
3923ca5
Compare
lforst
approved these changes
Aug 13, 2024
Lms24
force-pushed
the
prepare-release/8.26.0
branch
2 times, most recently
from
843a50d
to
cf38e46
Compare
Lms24
force-pushed
the
prepare-release/8.26.0
branch
from
cf38e46
to
2d4e4f5
Compare
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.
No description provided.