-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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 7.39.0 #7284
Merged
Merged
Conversation
This file contains 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
Member
Lms24
commented
Feb 27, 2023
•
edited
Loading
edited
- changelog entry for 7.39.0
- re-add changelog for 7.38.0 which seems to have been removed accidentally in chore: make unit tests cacheable, fix package graph #7108
[Gitflow] Merge master into develop
Normalize timeOffset entry in snapshots to avoid flakiness
Move the integration test for our WASM integration to our Playwright browser integration test suite. With this change we finally get rid of Puppeteer in our monorepo.
--------- Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
…7251) Add four integration tests for replays where errors occur: * error mode: * error to session transition once the error occurs * if the error is dropped, it shouldn't be linked in the replay event (see test comment about the problem with this scenario) * session mode * if an error occurs, make sure it's linked in the replay event * unless the error is dropped
`value` was being used as ms but start/end timestamps are in seconds. Changed start and end to be equal because LCP does not have a duration, it is a single point in time. --------- Co-authored-by: Lukas Stracke <lukas.stracke@sentry.io>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Co-authored-by: Abhijeet Prasad <aprasad@sentry.io>
Add a new SDK package to our monorepo: `@sentry/angular-ivy`. While this is technically a new SDK, its content and functionality is identical to `@sentry/angular`. Only the build configuration differs: * The Ivy SDK is built with Angular 12, allowing for a compatibility of NG12-15 * The Ivy SDK is built with `compilationMode: partial`, enabeling a build format that is compatible with Angular's Ivy rendering engine. * This means that `ngcc` no longer needs to step in at initial build time to up-compile the SDK. Which is good because `ngcc` will be removed in Angular 16 (angular/angular-cli#24720) * The Ivy SDK's build output follows the Angular Package Format (APF) v12 standard ([spec](https://docs.google.com/document/d/1CZC2rcpxffTDfRDs6p1cfbmKNLA6x5O-NtkJglDaBVs/preview)) which is very similar to APF 10 which we used before (see #4641 for more details) Because functionality-wise there's no difference to `@sentry/angular`, I opted to symlink the source files instead of duplicating them. The only exception is `sdk.ts` which needed some adaption for the new package, like setting the SDK name and adjusting the min version check. For the same reason, this new package currently doesn't contain tests. We'll need to reconsider this approach (symlinking and testing) if we ever need to make package-specific adjustments.
mydea
reviewed
Feb 27, 2023
mydea
reviewed
Feb 27, 2023
From 1.103.0 to 1.104.0 to 1.104.1
067708b
to
97094e4
Compare
mydea
approved these changes
Feb 27, 2023
Ah, ideally you can squash the changelog commits together before merging this (as they will remain in the state after being merged)! |
add sentence about ivy Apply suggestions from code review Co-authored-by: Francesco Novy <francesco.novy@sentry.io>
97094e4
to
cc119e3
Compare
Done |
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.