Repository navigation
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## beta #520 +/- ##
=======================================
Coverage 82.25% 82.25%
=======================================
Files 258 258
Lines 41833 41833
Branches 5608 5608
=======================================
Hits 34410 34410
Misses 7316 7316
Partials 107 107 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
🎉 This PR is included in version 4.26.0-alpha.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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
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.
Summary
Propagate the Node 22 local development requirement from
nexttobeta.Source:
nextat4bfb2d6a971a62e26a7ba61cc9434b8370ab0714.Destination:
betaat17f19798ecfb4457a908acfe746d170fc8ec6347.One missing ancestry commit and one unmatched patch; clean simulated merge changes two files (+8/-1). No patch-equivalence ambiguity.
Evidence
keeps latest and historical snapshots readable after deleting a candidate detection strategy. That file passes all 9 tests in isolation. Middleware 29 and scheduler 15 pass separately.Merge Danger
Door: Two-way; the development runtime requirement is reversible.
Blast Radius: Development.
Use a merge commit to preserve release-branch ancestry. Do not squash or rebase. Alpha propagation is separate and currently has a reviewed-state-service validation-policy conflict.