workflows: automatically create GitHub release when tagged #67
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.
Run
meson dist
on Linux in every build, because it's a good idea to test this and because the build job already installs the dependencies formeson setup
. Archive the artifact, then conditionally run a second job to do the release.This uses the same release-job pattern as OpenSlide Python, rather than starting a second workflow upon completion of the build workflow. This results in a skipped job in every PR's job list, but allows the passing of output variables between jobs.
Linux builds run in
ubuntu-latest
, not in a Fedora container, so the Autotools blobs in the source tarball will be generated on Ubuntu 22.04. That release has current versions of Autoconf and Automake, so this seems okay.