-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Comparing changes
Open a pull request
base repository: getsentry/sentry-javascript
base: develop@{1day}
head repository: getsentry/sentry-javascript
compare: develop
- 11 commits
- 84 files changed
- 8 contributors
Commits on Nov 10, 2025
-
feat(aws): Add
SENTRY_LAYER_EXTENSIONto configure using the lambda…… 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 <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for d26e1a9 - Browse repository at this point
Copy the full SHA d26e1a9View commit details -
fix(nextjs): Delete css map files (#18131)
closes #18125 We want to delete `*.map.css` files when `deleteSourcemapsAfterUpload` is enabled.
Configuration menu - View commit details
-
Copy full SHA for 10211f4 - Browse repository at this point
Copy the full SHA 10211f4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0054094 - Browse repository at this point
Copy the full SHA 0054094View commit details -
Merge pull request #18133 from getsentry/prepare-release/10.24.0
meta(changelog): Update changelog for 10.24.0
Configuration menu - View commit details
-
Copy full SHA for e861b4f - Browse repository at this point
Copy the full SHA e861b4fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 907546f - Browse repository at this point
Copy the full SHA 907546fView commit details -
Merge branch 'release/10.24.0'
getsentry-bot committedNov 10, 2025 Configuration menu - View commit details
-
Copy full SHA for d01b2a6 - Browse repository at this point
Copy the full SHA d01b2a6View commit details -
feat(node): Add
maxCacheKeyLengthto Redis integration (remove trun…Configuration menu - View commit details
-
Copy full SHA for 7019263 - Browse repository at this point
Copy the full SHA 7019263View commit details -
Merge pull request #18138 from getsentry/master
[Gitflow] Merge master into develop
Configuration menu - View commit details
-
Copy full SHA for 487e75e - Browse repository at this point
Copy the full SHA 487e75eView commit details -
feat(browser): Include Spotlight in development bundles (#18078)
This PR: - Splits the browser build output into separate development and production builds - References these two builds in the package.json exports - Adds a Rollup plugin to production builds which can strip out code wrapped with development-only magic comments - Adds the spotlight integration to the default integrations in development mode only - Also adds this plugin for browser bundles so spotlight doesn't get included in CDN bundles
Configuration menu - View commit details
-
Copy full SHA for 8b33254 - Browse repository at this point
Copy the full SHA 8b33254View commit details -
fix(core): Only consider exception mechanism when updating session st…
…atus from event with exceptions (#18137) This PR fixes an oversight in our session update logic when we update the SDK's session status while processing an error event. Previously, we'd always set `status: 'crashed'` as soon as the top-level `event.level` field was set to `'fatal'` (added in #15072). However, this disregarded the case where the level was initially `'fatal'` but later on the SDK or users decided to set the `event.exceptions.values[i].mechanism.handled` field to `true`. Simplest reproduction: ``` Sentry.captureException(new Error('test'), { captureContext: { level: 'fatal' } }); ``` This PR changes the update logic to only look at the event mechanisms if the event contained exceptions. I _think_ this is still compatible with #15072 because the PR suggests we only care about `event.level === 'fatal'` if no exceptions are on the event. But I'd appreciate a second pair of eyes on this (cc @timfish).
Configuration menu - View commit details
-
Copy full SHA for 6de4cba - Browse repository at this point
Copy the full SHA 6de4cbaView commit details -
ref(browser): Remove truncation when not needed (#18051)
Removes the remaining places where we truncate, although not needed. part of #17389
Configuration menu - View commit details
-
Copy full SHA for 02625ef - Browse repository at this point
Copy the full SHA 02625efView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff develop@{1day}...develop