Repository navigation
Fix POSIX restart fixture and prepare v1.0.31 - #190
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.
The restart argument test used a non-executable POSIX fixture, so Linux stopped at executable preflight instead of reaching argument validation. Give that temporary file owner read/write/execute permissions, matching the preceding executable-fixture test. Production behavior is unchanged.
Prepare 1.0.31 as the next unused stable version. The 1.0.30 candidate tag has no GitHub Release or updater entry and remains as a failed candidate record; it is not rewritten.
Validation: a focused Linux harness compiled against the actual desktop restart helper reproduces the missing-permission failure and passes after the fixture correction. The previous full Linux run completed all 6,969 enabled checks with this single failing test. Final master full CI and final Windows build must pass before tagging 1.0.31.