Revise workflows to automatically upload artifacts on new releases #276
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.
This PR revises the GH workflows to upload build artifacts to releases automatically. It should fix #271 among other things. Once a release is created and published the
release
workflow should build the artifacts and upload them automatically.Changes:
_ubuntu-noble
or_debian-12
suffixes are used to differentiate between them. @CosmicFusion is this accepted by Debian packaging tools?gzip
, i.eumu-launcher-1.1.4-zipapp.tar.gz
. Third-party scripts will need to be adjusted.sed
and I would be more than happy to revert these changes and only build tagged releases. The RPM spec was also adjusted for the same reason to checkout themanual_commit
if thetag
doesn't exist.build
workflow.The workflow for RPM packages fails currently because cloning the repo inside the specfile doesn't find the PR merge commit. If we want to handle that for PRs it will take some finessing, but I want to be sure it is needed before diving into it.