Repository navigation
Integrate single-binary updates and release RustChan 1.6.6 - #120
Merged
Merged
Conversation
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.
Native source installations previously depended on a separate update controller, and upgrading a 1.6.0 database could fail on the two newer post indexes. This integrates the controller/guardians into rustchan-cli, enforces durable writer admission and protocol-2 compatibility, and restores supported migration paths with full rollback. It also updates compatible Rust dependencies, pinned build tools and Debian container bases for 1.6.6.
Validation: macOS workspace (1,349 tests per library/application target plus CLI/policy/fixture/doc checks), Linux units (1,363), strict Clippy/docs, feature variants and seven packaging tests passed. Actual Linux executable fixtures passed signed synthetic installation, newest-controller handoff, post-migration full rollback and conservative same-boot recovery refusal. Complete Chromium: 287 expected, 38 skipped, zero unexpected or flaky results, original limits and zero retries.
Fixed the initial PR CI startup failure by hashing the exact executable before guardian spawn, keeping the five-second handshake and lease checks. A large-executable fixture reproduced failure before database creation and passed after the ordering fix. Native CLI validation also identified and fixed HTTPS-only readiness probing: the controller now queries the configured secure loopback listener with private instance/version checks. All five ordinary-account Linux CLI tests passed with unchanged assertions, parallel execution and deadlines. Linux fixtures strip only copied debug sections (28 allocated ELF sections verified identical); original debug executables remain preserved. All five required CI jobs and dependency audit passed on 6275439. GitHub Linux suites passed 1,363 tests each (six existing ignores) and all five CLI process tests passed.
Native Linux reboot/power-loss testing will be handled separately, as explicitly authorized for this release. The exact macOS executable from the final browser pass was not preserved during cleanup; its reports, source/build metadata and Linux fixtures remain, but exact-byte replay is limited. See docs/dependency-upgrade-1.6.6.md. Local AGENTS/Playwright tooling stays ignored and untracked.