Skip to content

Conversation

@stefanosiano
Copy link
Member

📜 Description

fixed merge conflicts

#skip-changelog

💡 Motivation and Context

💚 How did you test it?

📝 Checklist

  • I reviewed the submitted code.
  • I added tests to verify the changes.
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled.
  • I updated the docs if needed.
  • Review from the native team if needed.
  • No breaking change or entry added to the changelog.
  • No breaking change for hybrid SDKs or communicated to hybrid SDKs.

🔮 Next steps

@stefanosiano stefanosiano changed the title fixed merge conflicts Fix main merge Jul 1, 2024
@stefanosiano stefanosiano marked this pull request as ready for review July 1, 2024 19:19
@github-actions
Copy link
Contributor

github-actions bot commented Jul 1, 2024

Performance metrics 🚀

  Plain With Sentry Diff
Startup time 427.96 ms 486.62 ms 58.66 ms
Size 1.70 MiB 2.29 MiB 599.57 KiB

Previous results on branch: fix/main-merge-v8

Startup times

Revision Plain With Sentry Diff
2f9bcfb 430.06 ms 509.27 ms 79.21 ms

App size

Revision Plain With Sentry Diff
2f9bcfb 1.70 MiB 2.29 MiB 599.57 KiB

Copy link
Member

@adinauer adinauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The clear call should probably only go to the default write scope, other than that LGTM.

@stefanosiano stefanosiano merged commit 437936e into 8.x.x Jul 2, 2024
@stefanosiano stefanosiano deleted the fix/main-merge-v8 branch July 2, 2024 08:01
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.

4 participants