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: Update CHANGELOG for 8.1.0 #12062

Merged
merged 24 commits into from
May 16, 2024
Merged

meta: Update CHANGELOG for 8.1.0 #12062

merged 24 commits into from
May 16, 2024

Conversation

Lms24
Copy link
Member

@Lms24 Lms24 commented May 16, 2024

No description provided.

github-actions bot and others added 24 commits May 13, 2024 15:41
[Gitflow] Merge master into develop
See #11140


Closes #9119

---------

Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
Just to ensure we do not regress here.
Request isolation should work even without tracing (which means, even
without the express integration added - that is only added when tracing
is enabled, today!).

Really, the only thing missing should be `transactionName`.
Just a test showing how stuff behaves if:

1. `init` is called without DSN
2. `httpIntegration` is manually added
3. `init` is called again, later, with DSN

---------

Co-authored-by: Andrei <168741329+andreiborza@users.noreply.github.com>
fix(aws-serverless): Add `awslambda-auto` to `package.json` exports
Just noticed that there's not really a reason to have the two separate
warnings. Let's save some bytes.
…tion` options (#12023)

This patch forward-ports the `interactionsSampleRate` option for
`browserTracingIntegration` introduced in 7.110.0 to v8. Looks like we
missed this when forward-porting the INP implementation as reported in
#12006, probably because these two things happened in parallel.
)

To ensure all instrumentation is using the newest version of
`@opentelemetry/instrumentation` that has proper ESM support etc.
We had this as TBD. I checked with @ryan953 and put the version that we
want in, plus a disclaimer.
…2017)

The prior fix was incomplete, because we were still using
`getDefaultIntegrations()` inside of node's `init`, so the deps where
pulled in anyhow.

Furthermore, it seems that `preserveModules: false` for `@sentry/node`
also prevented this from working as expected.

So this PR does two things:

1. Set `preserveModules: true` so that tree-shaking can work as expected
(😿 )
2. Expose a new `initWithoutDefaultIntegrations` method from
`@sentry/node` which AWS uses, which avoids including any integrations
by default. You have to pass your own `defaultIntegrations` to it.

This is not the prettiest solution, but I couldn't think of anything
much better 😬 I also added a size-limit entry to keep track of this.
…2022)

Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Extracted this out from
#12020

For whatever reason, this does not seemed to play well with how we run
the proxy server via ts-node. Looking into this more, this is actually
not really necessary at all, so I just stripped this out in favor of
just running the proxy as a `.mjs` file directly - works just as well!
Supersedes #11912

I just cleaned up and renamed this to align with other things
)

Also fixes the broken link for release-approvers.

---------

Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
…ngIntegration` options (#12023)" (#12048)

The reason for the revert is that we're concerned about 1. the usefulness and 2. the
name of this option and would like to revisit this without blocking the
8.1.0 release. This is not semver-breaking because in 8.0.0, this API
did not exist.
@Lms24 Lms24 requested review from a team, mydea, stephanie-anderson and s1gr1d and removed request for a team and stephanie-anderson May 16, 2024 07:48
@Lms24 Lms24 requested a review from andreiborza May 16, 2024 07:48
@Lms24 Lms24 changed the base branch from develop to master May 16, 2024 07:57
@Lms24 Lms24 requested a review from a team as a code owner May 16, 2024 07:57
@Lms24 Lms24 merged commit b135be6 into master May 16, 2024
28 checks passed
@Lms24 Lms24 deleted the prepare-release/8.1.0 branch May 16, 2024 08:36
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.

None yet

6 participants