New version of all of sentry (7.42.0) broke the build #167
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
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
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.
We've tested your project with an updated dependency and the build failed.
This version is either within the version range you specified or you haven't specified a version/range. To be able to test your project with the new version, we've taken the liberty of pinning the version for this branch and pull request.
Unfortunately, we encountered failing tests after pinning. This means that this new version is not compatible with your project and the test failure will potentially also happen on fresh installs.
If you have correctly specified a semantic versioning version range, you should probably also file an issue with the upstream project as they might have released an update that's breaking SemVer rules, which is not cool. (But then again, not all projects explicitly follow SemVer)
We've left the pull request open for you to investigate this issue. Please don't merge it as is, because, again, we've pinned the version of @sentry/node for this test run.
What changed?
✳️ @sentry/node (^7.37.2 → 7.42.0) · Repo · Changelog
Release Notes
7.42.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 47 commits:
release: 7.42.0Merge pull request #7389 from getsentry/prepare-release/7.42.0meta(changelog): Update changelog for 7.42.0fix(tracing): Record LCP and CLS on transaction finish (#7386)feat(tracing): Track PerformanceObserver interactions as spans (#7331)feat(core): Emit hooks for transaction start/finish (#7387)test(replay): Add integration tests for input masking on change (#7260)feat(replay): Attach an error `cause` to send exceptions (#7350)ref(node): store split file in cache for contextlines (#7383)feat(core): Add lifecycle hooks (#7370)ref(browser): Improve type safety of breadcrumbs integration (#7382)fix: Make redux integration be configurable via normalizeDepth (#7379)ref(node): Partially remove dynamic `require` calls (#7377)adress reviewfix: Make redux integration be configurable via `normalizeDepth`ref(node): parallelize disk io when reading source files for context lines (#7374)ref(tracing): Revert conditional exports usage (#7372)test(replay): Add test for session max age handling (#7362)feat(replay): Consider user input in form field as "user activity" (#7355)feat(nextjs): Connect traces for server components (#7320)feat(tracing): Expose cancelIdleTimeout and add option to make it permanent (#7236)ref(replay): Handle checkouts more explicitly (#7321)chore(sveltekit): Add boilerplate SvelteKit SDK package (#7365)test(replay): Make tests less flaky (#7368)fix: Ensure `originalException` has type `unknown` (#7361)ref(tracing): Re-organize exports for node/browser (#7345)uuids suck as transactionsfeat(replay): Update rrweb to 1.105.0 & add breadcrumb when encountering large mutation (#7314)test(replay): Add tests for session expiration (#7253)fix(core): Avoid using `Object.values()` (#7360)test(e2e): Publish otel-node package tarballs (#7351)docs: Update replay docs for end of beta (#7349)test: Fix flaky droppedError test (#7337)assert on buildAdd e2e teststest: Run playwright tests in parallel (#7334)feat(tracing): Move common tracing code to core (#7339)Merge branch 'develop' into lforst-connected-traces-servercomponentsMerge pull request #7336 from getsentry/lforst-thorough-nextjs13-testschore(angular-ivy): Update Readmes (#7304)fix?explainMerge pull request #7338 from getsentry/masterMerge branch 'release/7.41.0'workersrev yarn lockrefineDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands