feat: restore purpose-specific GitHub Action boundaries - #72
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
1 participant
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
Restore consumer-facing GitHub Action boundaries for release-tool operations that were incorrectly expanded into shell-heavy workflow code during the repository migration.
Adds public composite Actions for:
These Actions delegate to the release-tool CLI and reuse the existing internal version/bootstrap logic, so consumers no longer hard-code a release-tool version or duplicate PHAR download/checksum shell.
Also bumps the product version to 0.11.3 and extends acceptance coverage for the explicit public Action contracts.
This follows up on LibreSign/libresign#8679.