Repository navigation
merge queue: checking #357 on main (f119b3f), stacked on #390, #377 and #372 - #395
Closed
mergify[bot] wants to merge 22 commits into
Closed
mergify[bot] wants to merge 22 commits into
mergify[bot] wants to merge 22 commits into
Conversation
Test-First: src-tauri/src/delivery_recovery/restore.rs::foreign_backup_never_replaces_the_journal_database Test-First: src-tauri/src/delivery_recovery/restore.rs::modified_backup_never_replaces_the_journal_database Co-Authored-By: Codex (GPT-5) <noreply@openai.com>
Test-First: src-tauri/src/delivery_recovery/restore.rs::journal_bound_backup_restores_before_write_resume Test-First: src-tauri/src/delivery_recovery/restore.rs::restore_is_refused_after_writes_resumed Co-Authored-By: Codex (GPT-5) <noreply@openai.com>
No-Test: append-only activity handoff Co-Authored-By: Codex (GPT-5) <noreply@openai.com>
…tion The reader refactor made restore_from_reader borrow the backup file, so the handle stayed open across replace_file. Take the reader by value and drop it before the replace, as the comment above it promises. Test-First: src-tauri/src/db_restore.rs::db_restore::tests::restore_closes_the_source_before_replacing_the_destination Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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>
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
Regression-For: 32148db
The user chose option A for E20 on 2026-10-04 in the orchestrator session: v1.5.0 is an app release through PR -> gates -> Mergify queue, continuous mode ships off and not release-eligible, and the user attests acceptance himself. PR #372 review B blocked because docs/PLAN.md still listed E20 as open. No-Test: documentation only Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
No-Test: generated activity record
No-Test: conflict resolution only; existing coverage follows in prepush
No-Test: generated activity record
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.
🎉 This pull request has been checked successfully and will be merged soon. 🎉
#357 is queued for merge on branch main (f119b3f).
Stacked behind 3 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 #357.
Queued ahead of this batch:
This pull request has been created by Mergify to speculatively check the mergeability of #357.
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