-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
meta(changelog): Update changelog for 10.24.0 #18133
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
Merged
Merged
+1,036
−725
Conversation
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
[Gitflow] Merge master into develop
…ed (#18019) Pass `ignoreCSSAttributes` with `background-imgae` to ignore background images when `blockAllMedia` is enabled. `ignoreCSSAttributes` was expanded in [this PR](getsentry/rrweb#252) so that it also works for inline styles.
Enabling eslint rules for RegEx in `dev-packages`. This is a part of this (now closed) PR: #18053 The first commit contains all changes that were automatically made with `--fix`, the second commit contains the manual changes.
- Fixing some of the types according to the specs.
…tric` (#18088) - Adds top level options for `enableMetrics` and `beforeSendMetric`. - Kept the experimental flags for now to stay backwards compatible, but added a deprecation note and todo comments for removing them in v11. - Updated all the tests to use the top-level flag. - Had to refactor the `_INTERNAL_captureMetric` function since it broke the complexity threshold of our linter > [!WARNING] > `enableMetrics` now defaults to `true`, so theoretically this PR is behaviourally breaking.
We need to stop accessing params within our wrapper templates as this can break statically rendered pages and cause cache busts in dynamic pages. Opened #18115 to investigate other ways of handling the functionality we're removing here. closes #18097 closes #17431 Note: There's some unused code in the utils that I did not delete as we might be able to reuse this in #18115
I can't reproduce the flakiness locally, I logged a few things on CI runs and it seems while the fetch spans does get created, it doesn't get created on the middletrasnaction. This is similar to what the note is saying in dev-mode, for it to be less flakey I'm asserting if it either has the span on the right transaction or if it got created in a separate transaction. Ideally we want it to be created within the middleware transaction but it seems like there is a timing issue preventing it from being picked up there. At any case this seems to reduce or eliminate the chances of failed runs, previously it would fail consistently but with this it didn't fail in 5 runs so far.
… layer extension via env variables (#18101) Our recommended approach for the aws sdk is to use our Lambda layer. When the Lambda layer is used, it would previously automatically set up the layer extension. This can be disabled by setting `useLayerExtension: false` during init, but when using the layer with our auto-wrapping as per recommendation, it wasn't possible to opt out of using the extension. This PR adds `SENTRY_LAYER_EXTENSION` that can be used to opt out of the extension. --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
closes #18125 We want to delete `*.map.css` files when `deleteSourcemapsAfterUpload` is enabled.
Contributor
size-limit report 📦
|
Contributor
node-overhead report 🧳Note: This is a synthetic benchmark with a minimal express app and does not necessarily reflect the real-world performance impact in an application.
|
andreiborza
reviewed
Nov 10, 2025
99eb4c8 to
59028df
Compare
59028df to
0054094
Compare
andreiborza
approved these changes
Nov 10, 2025
Member
andreiborza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ty for taking care of the release!
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.