Repository navigation
Make atomic project publish resilient - #67
Merged
Merged
Conversation
Visual recap — skippedThe visual recap job did not run for this pull request. This is informational only and does not block the PR. Recap skipped for |
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.
Linked issue
Closes #22
Observable behavior
Project publication now moves the previous output into a collision-safe backup path before promoting staged output. A stale backup from an interrupted run no longer prevents a valid build from publishing, and a failed promotion still restores the previous tree.
Proof
cargo +stable fmt --all --checkcargo +stable clippy --all-targets --all-features --locked -- -D warningsLUAU_BIN=... LUAU_ANALYZE_BIN=... cargo +stable test --test cli_project --lockedScope
The existing staged-write and deterministic-output contract remains unchanged; this closes the stale-backup collision in the publish path.