Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

feat(flags): add Unleash integration #14947

Closed
wants to merge 29 commits into from
Closed

feat(flags): add Unleash integration #14947

wants to merge 29 commits into from

Conversation

aliu39
Copy link
Member

@aliu39 aliu39 commented Jan 8, 2025

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

  • If you've added code that should be tested, please add tests.
  • Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

mydea and others added 29 commits December 16, 2024 10:29
In order for us to have size-limit comparison etc, we need to ensure CI
runs on v8 & v9 branches too.

Picking this from develop so we also have this on v8 branch!
This release also publishes the AWS lambda layer under the current,
non-version-suffixed layer since it's lagging behind since `8.42.0` with
the introduction of the v8-suffixed layer.
The v8 branch should not publish to the latest layer.
#14709)

We should normalise all paths in ANR events if an appRoot path is
supplied. This is important for the Electron SDK where we normalise
around the app path to keep usernames out of reported events.

Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Conor O'Brien <conor.w.ob@gmail.com>
…#14741)

This isn't exported in types-hoist/index, but we found users can still
import it from a `build/` file. Discussed with @billyvg we don't want
users to accidentally import it this way.

Note we currently use this type in sentry, until
getsentry/sentry#81954 is rolled out.
meta(changelog): Update changelog for 8.46.0
#14755)

Backport of #14753:

Bump
[@prisma/instrumentation](https://github.com/prisma/prisma/tree/HEAD/packages/instrumentation)
from 5.19.1 to 5.22.0.

See https://github.com/prisma/prisma/releases/tag/5.22.0 for release
notes.

This is to take advantage of the following change in 5.22.0:

> In our ongoing effort to stabilize the tracing Preview feature, we’ve
made our spans compliant with OpenTelemetry Semantic Conventions for
Database Client Calls. **This should lead to better compatibility with
tools such as DataDog and Sentry** [emphasis added by me].

There's also this change in
[5.21.0](https://github.com/prisma/prisma/releases/tag/5.21.0):

> The `tracing` Preview feature now has full support for MongoDB with
previously missing functionality now implemented. This is a part of the
ongoing effort to stabilize this Preview feature and release it in
General Availability.

The @dependabot PR for `@prisma/instrumentation` updates this to 6.0.0,
which unfortunately drops Node.JS v18 support, so it isn't suitable for
Sentry v8: #14624
backport to `v8` of #14766

---------

Co-authored-by: Max Malm <benjick@dumfan.net>
One more release before holidays to get out some v8-backported changes
…ided to `TraceDirective` (#14828)

Backport of #14778

---------

Co-authored-by: Artur <arthurandrosovich@gmail.com>
@aliu39 aliu39 closed this Jan 8, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants