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 v8.0.0-alpha.7 #11308

Merged
merged 7 commits into from
Mar 27, 2024

Conversation

mydea
Copy link
Member

@mydea mydea commented Mar 27, 2024

Pending on #11306...

@mydea mydea requested review from lforst and AbhiPrasad March 27, 2024 12:40
@mydea mydea self-assigned this Mar 27, 2024
@mydea mydea force-pushed the prepare-release/8.0.0-alpha.7 branch from ea4bbbc to f1bcb5c Compare March 27, 2024 12:41
mydea and others added 3 commits March 27, 2024 12:51
Let's see if that fixes the publishing issue... (Note that this was
never there, but maybe this is a problem...)
With this change, there are two remaining references to
node-experimental.

1. nextjs, which is handled by
#11016
2. express integration tests, which I will address after
#11285 gets merged

Once those two are done, we can remove the old node packages entirely!
This is quite the refactor, I recommend reading through the migration
docs to understand what the user facing API should be.

1. Remove deprecated SDK init via options

We used to initialize the SDK via Gatsby plugin options in the Gatsby
SDK. This is very restrictive though, and due to how Gatsby serializes
it's options can lead to bugs. Later on in v7 of the SDK we introduced a
`sentry.config.js` approach
([docs](https://docs.sentry.io/platforms/javascript/guides/gatsby/)).
This PR removes support for the plugin option deprecation.

- Remove automatic adding of `browserTracingIntegration`

Because of the plugin option initialization, we used to add
`browserTracingIntegration` integration automatically via SDK init. v8
removes this because of bundle size + we don't have good routing
instrumentation for gatsby.

- Upgrade gatsby webpack plugin to 2.0, and add option to configure it's
usage

resolves #9837 - I
called the option to control this `enableClientWebpackPlugin`.
@mydea mydea force-pushed the prepare-release/8.0.0-alpha.7 branch from f1bcb5c to be4bfff Compare March 27, 2024 13:18
@mydea mydea changed the base branch from develop to master March 27, 2024 13:19
@mydea mydea force-pushed the prepare-release/8.0.0-alpha.7 branch from be4bfff to 2f6291d Compare March 27, 2024 13:22
@mydea mydea marked this pull request as ready for review March 27, 2024 13:22
Copy link
Contributor

size-limit report 📦

Path Size
@sentry/browser (incl. Tracing, Replay, Feedback) 80.54 KB (added)
@sentry/browser (incl. Tracing, Replay) 71.88 KB (added)
@sentry/browser (incl. Tracing, Replay with Canvas) 75.68 KB (added)
@sentry/browser (incl. Tracing, Replay) - with treeshaking flags 65.43 KB (added)
@sentry/browser (incl. Tracing) 36.71 KB (added)
@sentry/browser (incl. browserTracingIntegration) 36.71 KB (added)
@sentry/browser (incl. feedbackIntegration) 31.38 KB (added)
@sentry/browser (incl. feedbackModalIntegration) 31.5 KB (added)
@sentry/browser (incl. feedbackScreenshotIntegration) 31.51 KB (added)
@sentry/browser (incl. sendFeedback) 27.45 KB (added)
@sentry/browser 22.61 KB (added)
CDN Bundle (incl. Tracing, Replay, Feedback) 74.98 KB (added)
CDN Bundle (incl. Tracing, Replay) 69.8 KB (added)
CDN Bundle (incl. Tracing) 36.35 KB (added)
CDN Bundle 23.97 KB (added)
CDN Bundle (incl. Tracing, Replay) - uncompressed 219.11 KB (added)
CDN Bundle (incl. Tracing) - uncompressed 109.67 KB (added)
CDN Bundle - uncompressed 70.94 KB (added)
@sentry/react (incl. Tracing, Replay) 71.86 KB (added)
@sentry/react 22.64 KB (added)

@mydea mydea merged commit 11cb00e into master Mar 27, 2024
91 checks passed
@mydea mydea deleted the prepare-release/8.0.0-alpha.7 branch March 27, 2024 13:45
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.

3 participants