[codex] Add AppImage release workflow#1230
Closed
vitaly-zdanevich wants to merge 1 commit into
Closed
Conversation
c3f43f7 to
30065d5
Compare
30065d5 to
fe0ec90
Compare
Author
|
Closing this older draft as superseded by #1231, which contains the current squashed AppImage CI work and green validation. |
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.
Adds AppImage packaging support and a GitHub Actions workflow that builds an AppImage whenever a GitHub Release is published. The workflow also supports manual dispatch after it is present on the default branch.
What changed:
Validation:
Note: GitHub Actions artifacts are downloaded as zip archives. On a published GitHub Release, the workflow attaches dist/*.AppImage to the release with gh release upload, so release users download the .AppImage directly. GitHub will not workflow_dispatch a brand-new workflow until it exists on the default branch, so the fork CI validation used a temporary branch-only push trigger that is not part of this PR.