Add custom release artifact names - #1
Draft
kelindi wants to merge 1 commit into
Draft
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
artifact-nameinput for custom published DMG or ZIP filenames.Why
Releases built directly from an Xcode project currently use Amore's product-derived artifact name. Consumers that need a versioned or otherwise custom download filename have no way to name the generated artifact before it is uploaded.
When
artifact-nameis set, the action now builds the signed/notarized artifact locally with--output, renames it, and publishes that existing artifact. Build-only flags stay on the first invocation, while release metadata and channel flags stay on the publishing invocation.Validation
bash -n scripts/release.sh tests/release_test.shtests/release_test.shaction.ymlwith Ruby YAMLgit diff --check