Repository navigation
chore: harden release packaging and CLI - #44
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.
Summary
--help,--version, and--option handling--no-file-teesuppress console-backend file mirroring and avoid dry-run temporary workspacesWhy
The release workflow previously suppressed packaging errors, referenced the wrong licence filename, did not validate generated archives, and published no checksums. CLI and documentation behavior also diverged around option parsing, file logging, and dry-run side effects.
This change makes incomplete releases fail before publication and aligns documented behavior with the implementation.
Validation
make test(12 test scripts)README.mdgit diff --checkCloses #34