Repository navigation
Fix restore races and update rustls before v0.3.0 - #394
Merged
Merged
Conversation
adamXbot
marked this pull request as ready for review
October 16, 2026 02:09
This was referenced Oct 16, 2026
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.
What and why
Backup restore could replace the database while Wayback, policy or import work was running, and a sync started during upload bypassed its early check. Both backends now reject restore before upload and immediately before replacement while registered asynchronous writers remain live. Rust checks under the same connection lock as the restore; detached tasks register before spawning. The Node rollback also protects worker commits, per-app requests and background writes. The legacy Node Wayback algorithm is unchanged.
Update only rustls from 0.23.45 to 0.23.46 in both shipping lockfiles and regenerate notices, resolving RUSTSEC-2026-0346 through -0349 without weakening cargo-audit. This follows AGENTS.md's narrow advisory-fix procedure.
How it was verified
Remaining release gates
This PR does not change GitHub administration settings. The authenticated account has push access but no administration access. An administrator must add the CODEOWNERS human owner AdamXweb as a required macos-signing reviewer, retain the v* tag restriction, and add e2e-rust from GitHub Actions to ruleset 17555639. The strict repository audit still fails those two checks and cannot verify the secret-scanning configuration with this account.
Review and merge only after current CI passes. Signed/notarized candidate verification and the human signing approval remain required before publication. No release was published or signing gate bypassed.