Skip to content
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

meta(changelog): Update changelog for 9.7.0 #15724

Closed
wants to merge 14 commits into from
Closed

Conversation

s1gr1d
Copy link
Member

@s1gr1d s1gr1d commented Mar 18, 2025

No description provided.

mydea and others added 13 commits March 17, 2025 14:39
…15702)

Fixes part of #15518

We have been using the deprecated `new Span()` syntax for tests in OTEL.

This PR changes this to instead use a proper tracer, which is also
supported in v2 of otel.
In #15530 I added
types for the log envelope and log item.

This PR comes and explicitly references that these added types were otel
logs. For more details, see the logs spec in develop:
getsentry/sentry-docs#12920.


Note I used `Otel` everywhere here, but I'm also fine with switching to
`OpenTelemetry`.
…5710)

Previously, the Sentry server config was added by adding another entry
point in the rollup options of Vite. Since Nuxt changed
`preserveModules` to `true`, this did not work anymore. The aim of this
change in Nuxt is to avoid duplicating what the Nitro build would do.

This means, that we now don't change the Rollup options in Vite anymore
(affects Nuxt as a whole) but only the Rollup options during the Nitro
build.

The added plugin will emit a new file and returns the Sentry config code
there.

fixes #15628
[Gitflow] Merge master into develop
Adding tests for the [nightly
channel](https://nuxt.com/docs/guide/going-further/nightly-release-channel)
of Nuxt.

Right now, they are failing - will merge this PR once they are not
failing anymore. See issue:
#15628

This PR adds fixes to the tests should not fail anymore:
#15710
@s1gr1d s1gr1d requested a review from AbhiPrasad March 18, 2025 16:37
Copy link
Contributor

github-actions bot commented Mar 18, 2025

size-limit report 📦

Path Size % Change Change
@sentry/browser 23.15 KB added added
@sentry/browser - with treeshaking flags 22.94 KB added added
@sentry/browser (incl. Tracing) 36.21 KB added added
@sentry/browser (incl. Tracing, Replay) 73.39 KB added added
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 66.81 KB added added
@sentry/browser (incl. Tracing, Replay with Canvas) 78.01 KB added added
@sentry/browser (incl. Tracing, Replay, Feedback) 90.57 KB added added
@sentry/browser (incl. Feedback) 40.3 KB added added
@sentry/browser (incl. sendFeedback) 27.79 KB added added
@sentry/browser (incl. FeedbackAsync) 32.58 KB added added
@sentry/react 24.97 KB added added
@sentry/react (incl. Tracing) 38.1 KB added added
@sentry/vue 27.4 KB added added
@sentry/vue (incl. Tracing) 37.9 KB added added
@sentry/svelte 23.18 KB added added
CDN Bundle 24.36 KB added added
CDN Bundle (incl. Tracing) 36.26 KB added added
CDN Bundle (incl. Tracing, Replay) 71.27 KB added added
CDN Bundle (incl. Tracing, Replay, Feedback) 76.45 KB added added
CDN Bundle - uncompressed 71.19 KB added added
CDN Bundle (incl. Tracing) - uncompressed 107.57 KB added added
CDN Bundle (incl. Tracing, Replay) - uncompressed 218.83 KB added added
CDN Bundle (incl. Tracing, Replay, Feedback) - uncompressed 231.39 KB added added
@sentry/nextjs (client) 39.38 KB added added
@sentry/sveltekit (client) 36.63 KB added added
@sentry/node 142.29 KB added added
@sentry/node - without tracing 95.7 KB added added
@sentry/aws-serverless 120.06 KB added added

@s1gr1d
Copy link
Member Author

s1gr1d commented Mar 19, 2025

closed in favor of 9.6.1: #15727

Waited for a PR that would be the semver feature (hence v9.7.0) but it will be merged later: #15635

@s1gr1d s1gr1d closed this Mar 19, 2025
@s1gr1d s1gr1d deleted the prepare-release/9.7.0 branch March 19, 2025 08:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants