Repository navigation
feat: add managed replacement and configurable idle waits (0.8.0) - #28
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.
Re-uploading a changed release directory currently fails with
FILE_EXISTS, and a short client response wait can report failure while the server is still committing. This adds configurable 10-minute client idle waits and opt-in replacement of managed artifacts.--allow-replace [selector]/ServerOptions.allowReplacefor files and whole directories: global, exact name or existing release-template syntax. Off by default; unmanaged, modified, symlink and case-alias destinations remain protected. Legacy--replace-nameremains compatible.fs-native-extensions, for native exchange. It loads only when directory replacement is needed.The first directory replacement durably marks private state so 0.7.x refuses it before recovery can remove newer records. Downgrading then requires a matching pre-replacement backup of state and public files. For file-only state, recover pending 0.8 transactions and stop cleanly before downgrading.
Validation at signed head
cd3a67e2a6cc0729def989c4cd145a5b7773645a: all 10 PR checks pass, including Node 22/24 and Bare on Linux/macOS, quality/package, and CodeQL. Parent-run full suites each pass 722 tests on macOS Node 22/24 and Bare, plus isolated Linux ARM64 Bare. Node runs exercise real 0.3.0/0.6.3 clients and actual 0.7 startup refusal. Hard-process SIGKILL recovery passes on Node 22/24. Package installation, globally installed Node/Bare CLI and release-tag guards pass; runtime dependency audit reports zero vulnerabilities. Independent Harness review and both correction reviews are clean at the current head. The retention regression was reproduced failing before its fix.Extra ARM64 validation exposed two pre-existing Bare safeguards with incorrect native flag fallbacks: Linux ARM no-follow and macOS exclusive creation. Both now use one shared lookup with real-filesystem regression tests. No additional runtime dependency or wire change is involved.
QVAC rollout drafts: https://github.com/tetherto/qvac-app/pull/2826 and https://github.com/tetherto/qvac-app/pull/2827. They remain drafts until 0.8.0 is published. The longer client wait alone needs no server restart; directory replacement needs server 0.8.0 and the explicit operator setting.