-
Notifications
You must be signed in to change notification settings - Fork 0
Doing a release
This is for me, but I don't want to forgor.
Just copy the build artifact from the latest action and place it in the release. This is only for x86-64 for now but an aarch64 release should be added eventually.
This also needs to be added to appimagehub (which can be done by making a commit to the repo once the project is setup for it)
These are also using CI currently and every time a push is done the --edge branch gets updated in the snap store. To push it forward just promote the releases in the store.
For now, this is a manual process but will be improved.
In preparation, the latest https://github.com/TylerCode/cycles/actions/workflows/archive-repo.yml artifacts need to be downloaded, extracted, and put somewhere that a link can be obtained. (It's super janky but after a few releases we'll just make the whole thing into an action and not do this anymore)
A checksum also needs to be performed so that it can be used for the build
sha256sum repo-archive.tar.gz
Take the link and she sha256sum into the us.tylerc.cycles.yaml file.
sudo flatpak install -y flathub org.flatpak.Builder
sudo flatpak remote-add --user --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
sudo flatpak --user install -y --noninteractive flathub org.freedesktop.Platform//23.08 org.freedesktop.Sdk//23.08 org.freedesktop.Sdk.Extension.golang//23.08
flatpak run org.flatpak.Builder --force-clean --sandbox --user --install --install-deps-from=flathub --ccache --mirror-screenshots-url=https://dl.flathub.org/repo/screenshots --repo=repo builddir us.tylerc.cycles.yaml