Uh oh!
There was an error while loading. Please reload this page.
meta(changelog): Update changelog for 9.0.0-alpha.2 - #15323
Merged
Conversation
…ions` (#15246) This pull request includes changes to enhance the configuration options for managing Sentry source maps in a Nuxt.js project. The most important changes include adding new options to suppress logs, handle errors during release creation, and manage Sentry releases. Enhancements to Sentry source maps configuration: * [`packages/nuxt/src/common/types.ts`](diffhunk://#diff-199725da81bbdbb2e85f3dfe2b1a2bf453b4c9755059e5050815d7fcde2f59a5R11-R41): Added `silent`, `errorHandler`, and `release` options to the `SourceMapsOptions` type to provide more control over logging, error handling, and release management. * [`packages/nuxt/src/vite/sourceMaps.ts`](diffhunk://#diff-d511a0577f152ed6476e519722483c904cd2878586fdcd27f71c5587036bee37R96-R98): Updated the `getPluginOptions` function to include the new `silent`, `errorHandler`, and `release` options, allowing them to be used during the source maps upload process. Before submitting a pull request, please take a look at our [Contributing](https://github.com/getsentry/sentry-javascript/blob/master/CONTRIBUTING.md) guidelines and verify: - [x] If you've added code that should be tested, please add tests. - [x] Ensure your code lints and the test suite passes (`yarn lint`) & (`yarn test`). --------- Co-authored-by: Sigrid Huemer <32902192+s1gr1d@users.noreply.github.com>
[Gitflow] Merge master into develop
This PR adds the external contributor to the CHANGELOG.md file, so that they are credited for their contribution. See #15246 --------- Co-authored-by: s1gr1d <32902192+s1gr1d@users.noreply.github.com> Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
This streamlines this a bit and should be good enough here.
- Related to #15008 Export helpers to avoid duplications in sentry/react-native. - RN PR getsentry/sentry-react-native#4466
Due to a change in the lifecycle of Svelte components in Svelte 5 (using Rune mode), our SDK can no longer leverage the `(before|after)Update` hooks to track component update spans. For v9, this patch therefore disables update tracking by default.
Removes a no longer necessary fallback check that we only needed in SvelteKit 1.26.0 or older. For Kit 2.x, we can rely on the `event.isSubRequest` flag to identify sub vs. actual requests in our request handler. fixes#15244
- adds a toolbar for cropping and annotations - changes from inline styles to multiple class names in BEM format With annotation option:  Without annotation option (to confirm that it looks the same as before):  Closes#15252
…15288) The debugging ability for Azure Functions when using Azure Static Web Apps is very limited. But as I could see some Sentry-related logs I **think** Sentry is generally initialized. However, server-related logs don't show up in Sentry. This is **probably** because the Azure Function finishes before the error can be sent to Sentry. By adding the Azure environment variable to check whether we should flush with a timeout, this should possibly fix the issue. Logs in Application Insights: 
…5299) This integration is removed in v9 so we do not need this code anymore. Noticed this by chance 😅
We use capitalized integration names everywhere, except here. Noticed this by chance, this is kind of breaking, so probably also should go into the migration guide - @lforst should I add this, but this will conflict with the big PR, so maybe we just add it there directly?
Co-authored-by: Francesco Gringl-Novy <francesco.novy@sentry.io>
This was still set differently in a few places. This PR unifies this so we do this consistently. For aws-serverless, we also still hard-coded the `AWSLambda` integration name, but this is already reflected via the `Aws` and `AwsLambda` integrations anyhow.
Rename the `hasTracingEnabled` utility function to `hasSpansEnabled`. The original name is causing confusion and doesn't represent what the function actually does: determining if the SDK is configured to record spans. This function does not check if trace propagation without span recording (or "Tracing without Performance") is enabled (which it basically always is).
When we first created the Svelte SDK, we wanted to measure how often it was used in a SvelteKit application. Therefore we added some SvelteKit detection logic to annotate events coming from the Svelte SDK. Since we have a SvelteKit SDK now, we don't need to track this anymore. Saves a few bytes, too. This patch therefore removes the detection and event processing logic
…tegration CDN bundle (#15303) Since we removed `debugIntegration` in v9, the `debug(.min).js` bundle now only contains `spotlightIntegration`, which is confusing, and doesn't follow the usual naming patter for integration CDN bundles. This patch therefore renames the bundle to `spotlight(.min).js`.
Adds all stores to the state object. closes#15232 Before, it could only hold the state of the currently changed store like: ```javascript // before { count: 0, name: 'Counter Store' } ``` Now, when having a counter and a cart store, it looks like this (using the store IDs as the object keys): ```javascript // now { cart: { rawItems: ['item'], }, counter: { count: 0, name: 'Counter Store', }, } ```
Ran both tests 100x in CI to check if the flakes are gone ([1](https://github.com/getsentry/sentry-javascript/actions/runs/13160819942/job/36729143461?pr=15311#step:14:80), [2](https://github.com/getsentry/sentry-javascript/actions/runs/13160819942/job/36729144129?pr=15311#step:14:82)). Seems so! The reason for the flake was that we didn't wait long enough until the Sentry SDK was intiialized before checking for it. closes#15269
…uests if they are not defined (#15316)
Lms24
approved these changes
Feb 6, 2025
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
8 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.