Uh oh!
There was an error while loading. Please reload this page.
meta(changelog): Update changelog for 9.0.0-alpha.1 - #15263
Merged
Conversation
It's 2025 now.
[Gitflow] Merge master into develop
[remove-unused](https://removeunused.com/) found more unused files, this time in `replay-internal` and `vercel-edge`.
Fixes: #15027 This PR adds support for lazily loaded components and routes inside `Suspend` on react-router pageloads / navigations.
In our internal Open Source Legal Policy, we decided that licenses don't require a data range. This also has the advantage of not updating the date range yearly.
In our internal Open Source Legal Policy, we decided that licenses don't require a data range. This also has the advantage of not updating the date range yearly.
ref getsentry/team-sdks#116 This PR implements a new client discard reason for `buffer_overflow`. This will be used to track when the internal breadcrumbs buffer overflows for the new logs product that we are working on. This is documented in develop here: getsentry/sentry-docs#12395 Note: The reason we have `buffer_overflow` as a separate item to `queue_overflow` is that in the future when we send log items in envelopes we'll increment `queue_overflow` for the transport queue. We want to differentiate between the transport queue and the internal buffer explicitly.
Since the default way of setting up the SDK and passing the Sentry options is by wrapping the SolidStart config with `withSentry`, the previous method of using the `sentrySolidStartVite` plugin is no longer supported.
- Include full key path rather than the top level key in title - Improve message for validation issues with no path - Add option to include extended issue information as an attachment
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15111 Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Link to the Sentry develop docs for explaining the LOGAF scale.
…oad (#15148) If `#reload` is called on an instance of `Bun.serve`, the Sentry intrumentation doesn't surive. This is because the Bun instrumentation works by using `Proxy` on the call to `Bun.serve`, which isn't called for a reload. We can't wrap the serve created by calling `Bun.serve` with a `Proxy` as Bun seems to do some internal checks using `instanceof` which break if the instance is now reporting itself as a `ProxyObject`.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15148 --------- Co-authored-by: AbhiPrasad <18689448+AbhiPrasad@users.noreply.github.com> Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
The `loadModule` function currently utilizes `require` to load modules starting from the `@sentry/core` directory. This approach is incompatible with package managers like pnpm, which do not hoist dependencies. Consequently, when another module, such as @sentry/nextjs, invokes `loadModule`, it fails to locate its own dependencies because the search initiates within the @sentry/core tree.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15139 --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Relax the assertion for the replay recording data test so that we allow arbitrary order but still assert on the exact amount and contents of the received recording items. closes#15167
example.com still seems flaky, let's avoid making requests to it
--------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
--------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Also align to use the same version everywhere, tilde-restricted.
This PR removes all the code and CI steps that were moved to `@sentry-internal/node-cpu-profiler`. --------- Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
- Relocated `extractNetworkProtocol` util and its unit test to `browser-utils`. - Modified `browserMetrics` test to assert the new metadata. - Added integration test --------- Signed-off-by: Kaung Zin Hein <83657429+Zen-cronic@users.noreply.github.com> Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Bumping our images to ubuntu-22.04, except for the `ubuntu-20.04-large-js` ones, as I guess those ones are custom - should look into those too then eventually. In a follow up, we can try to bump to 24.04, possibly, but I figured we can do this piece by piece.
) We used to have `shutdownTimeout` in the core client options, but this option only applies in node, so we can move it there. Also fixing a small unnecessary check I noticed along the way. This is technically breaking, but should not affect anybody as this option is not used (and documented) anywhere outside of node.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15161 --------- Co-authored-by: Lms24 <8420481+Lms24@users.noreply.github.com> Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Some more formatting changes to the migration docs, also remove todos where appropriate.
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15235 --------- Co-authored-by: Lms24 <8420481+Lms24@users.noreply.github.com> Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
We adapted this here but did not adapt the types: #15235
Related to #15231, I noticed that we today would not propagate traces in outgoing http requests if: 1. The user configures `httpIntegration({ spans: false })` 2. ..._or_ the user has a custom OTEL setup 3. _and_ the user does not add their own `HttpInstrumentation` Admittedly and edge case. More importantly, though, by actually adding distributed tracing information here, we are unblocked from potentially stopping to ship the http-instrumentation to users that do not need spans (and/or have a custom otel setup). --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
This test was still skipped. I un-skipped it and actually split this up into dedicated tests for clarity. Can't get electron to run successfully on CI (works locally for me...) so skipping it for now, until maybe @timfish can figure it out :D
Contributor
size-limit report 📦
|
lforst
approved these changes
Feb 3, 2025
lforst
reviewed
Feb 3, 2025
Uh oh!
There was an error while loading. Please reload this page.
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
18 participants
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.