Retry transient release package installs and verify them independently - #147
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.



A transient
Broken pipeduring Linux Homebrew installation required a manual release-job retry even though the published archive was valid. Add a shared installation helper for Homebrew and Scoop that retries recognized transient failures at most three times, with 10- and 30-second delays, and retains each attempt's output and exit code.The helper checks installation state before retrying. A completed install must match the exact release version and source commit; partial installs, integrity or permission failures, unknown errors, and version mismatches stop. Functional smoke tests and cleanup remain mandatory. Retries cover Wrighty installation only, not package-manager bootstrap, publication, uploads, or repository pushes.
Add the
verify-installationoperation to the existing Release workflow so changes can be tested from a branch against an already published immutable release. It reuses the release installation jobs, uses read-only repository access, and skips release credentials, publication, and package-manifest updates. Document the operation and add cross-platform failure-handling checks to CI.Validation:
v0.19.0-alphaon Linux/Homebrew, macOS/Homebrew, and Windows/Scoop, including exact version/commit verification, Local Markdown lifecycle and stored-state checks, and uninstall cleanup.git diff --checkpassed.