Ci/release assets - #541
Merged
Merged
Conversation
Run the Linux .deb, macOS and Windows workflows on published releases and upload their packages as release assets. Upload the Windows deploy folder as the Actions artifact instead of the zip, to avoid a zip nested inside the artifact zip. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Derive VERSION from git describe (release tag on release builds) and use it in the .deb and .dmg file names and the Actions artifact names. Fetch full history so tags are available, which also fixes the "notag" name of the Windows mandeye zip on push builds. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Contributor
Author
|
I accidentally merged it to upstream, not fork with out review. My bad. I think it can stay. |
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.
No description provided.