ref(flags/v8): rename unleash integration param #15344
Closed
Conversation
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
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 <[email protected]>
Co-authored-by: Conor O'Brien <[email protected]>
…#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
Backport of #14291 to v8
#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
#14740) Backporting the release docs for older branches.
backport to `v8` of #14766 --------- Co-authored-by: Max Malm <[email protected]>
One more release before holidays to get out some v8-backported changes
Backported deprecation of #14797
…ided to `TraceDirective` (#14828) Backport of #14778 --------- Co-authored-by: Artur <[email protected]>
The v8 suffixed layer lands in the release-registry every time we publish a release from the v8 branch which not only breaks https://github.com/getsentry/sentry/blob/c11f4c099257b2388d150f71fb39516e3d3f2328/src/sentry/integrations/aws_lambda/utils.py#L236-L253 but also ends up in the docs as the current version: when using the ARN dropdown https://docs.sentry.io/platforms/javascript/guides/aws-lambda/install/cjs-layer/. This removes the suffix so we get the current major published under the non-suffixed name. Follow-up task: #14842
backport of #15139 --------- Co-authored-by: Randolf J <[email protected]> Co-authored-by: Abhijeet Prasad <[email protected]>
This also needs to go into v8, I guess! --------- Co-authored-by: Luca Forstner <[email protected]>
Backport of #15161 --------- Signed-off-by: Kaung Zin Hein <[email protected]> Co-authored-by: Kaung Zin Hein <[email protected]>
Cutting a patch to address #15209
backport of #15171 Co-authored-by: chris-basebone <[email protected]>
…rumentation (#15237) backport of #15235 and #15241 --------- Co-authored-by: Tanner Linsley <[email protected]> Co-authored-by: Francesco Novy <[email protected]>
Co-authored-by: Francesco Gringl-Novy <[email protected]>
Backport of #14967 to v8. The diff here will shrink a lot when #15094 is merged. --------- Co-authored-by: Andrei <[email protected]>
Add a guard to the Svelte SDK's component update tracking feature to catch an error thrown by Svelte 5 in Runes mode. In Runes mode, components must not call the old `beforeUpdate` or `afterUpdate` lifecycle hooks.
…y and deprecated note
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
(Accidentally pointed at v8)