The builds described above (actions' artifacts) will disappear after some time (90 days by default). Also, users need to be signed-in to GitHub to be able to download them. So this is not a complete final solution, yet.
If you want to distribute the builds to users, you should upload them e.g. as "release" on GitHub or anywhere else.
For example, you can use it like this to replace files in snapshot
release:
steps:
- ...
- name: Release Artifacts
if: ${{ github.ref == 'refs/heads/master' }}
run: gh release --repo MY-ORGANIZATION/MY-PROJECT upload snapshot --clobber *.zip *.tar.gz
env:
GH_TOKEN: ${{ github.token }}
Note
|
Above example step overwrites the snapshot release files every time it is done, while the release tag stays the same. It works and is useful for snapshot releases. But it is not a normal release setup: "normal" release should be done once, building binaries from the proper tag, and the released files should not change later. Tweak above example as you wish, e.g. to build on specific tag and/or to create a new release every time by gh release create … .
|