Repository navigation
merge queue: checking #373 on main (f119b3f), stacked on #377 and #372 - #392
Closed
mergify[bot] wants to merge 11 commits into
Closed
mergify[bot] wants to merge 11 commits into
mergify[bot] wants to merge 11 commits into
Conversation
Rename the computed releaseEligible to continuousReleaseEligible (keep a deprecated alias for one release), add appReleaseEligible gated on the configuration and machineInterface phases plus the user's appReleaseAttested, and bump the report schemaVersion to 2 (E20 option A). Test-First: scripts/lib/continuous-readiness.test.mjs::app release is blocked without the user attestation Test-First: scripts/lib/continuous-readiness.test.mjs::app release attestation does not make continuous mode release-eligible Test-First: scripts/lib/continuous-readiness.test.mjs::app release still needs configuration and machine interface Test-First: scripts/lib/continuous-readiness.test.mjs::readiness report is schema version 2 Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The claim checked each dependency by bare id: more than 64 completed dependencies still claimed (the briefing reports truncated, unsatisfied) and a completed task of another project satisfied the gate. Extract one check shared in semantics with the briefing: max 64, own project only. Test-First: src-tauri/src/store/continuous.rs::store::continuous::tests::claim_refuses_more_than_64_completed_dependencies Test-First: src-tauri/src/store/continuous.rs::store::continuous::tests::claim_refuses_completed_dependency_from_another_project Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Reuses the W3-03a drill kit: polls the updater phases, tolerates the relaunch gap, compares sessions and the recovery journal before/after. Test-First: scripts/lib/updater-drill.test.mjs::successful update passes after phases and relaunch with surviving sessions Test-First: scripts/lib/updater-drill.test.mjs::failed update needs an error phase with a message and no relaunch Test-First: scripts/lib/updater-drill.test.mjs::cancelled update must return to a resting phase without relaunch Test-First: scripts/lib/updater-drill.test.mjs::a missing session fails the drill Test-First: scripts/lib/updater-drill.test.mjs::an unreachable app fails before any step Test-First: scripts/lib/updater-drill.test.mjs::journal summary records phase and hash but never the content Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Test-First: scripts/lib/updater-drill.test.mjs::successful update rejects an error state after relaunch Test-First: scripts/lib/updater-drill.test.mjs::worker evidence does not claim that an inactive row is a live session
Regression-For: 0deb226
No-Test: comment-only correction matching the updater session guard
Use the shared refusal vocabulary for the new dependency limit and route it through the canonical HTTP status mapper. Test-First: src-tauri/src/api.rs::api::continuous_refusal_prefix_is_a_conflict
Regression-For: 32148db
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.
✨ Pull request #390 with higher priority has been queued. The pull request #373 has been requeued. ✨
#373 is queued for merge on branch main (f119b3f).
Stacked behind 2 pull requests queued ahead of this batch, not part of it. These checks run on a tip that also carries their commits, so a failure here can come from them as much as from #373.
Queued ahead of this batch:
This pull request has been created by Mergify to speculatively check the mergeability of #373.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue rule
defaultfor merge:check-success = gates (linux)check-success = gates (windows)check-success = red-firstlabel != do-not-mergeRequired conditions to stay in the queue:
-conflict-draftbase = maincheck-success = gates (linux)check-success = gates (windows)check-success = red-firstlabel != do-not-merge