Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate publishing release binaries #23

Open
gnprice opened this issue Dec 8, 2022 · 1 comment
Open

Automate publishing release binaries #23

gnprice opened this issue Dec 8, 2022 · 1 comment

Comments

@gnprice
Copy link
Owner

gnprice commented Dec 8, 2022

Currently the process by which I accomplish #3 — which started today — is not hard, but it is a few extra steps:

  • (Have the release commit checked out.)
  • Run tools/build-release linux-x86.
  • Visit https://github.com/gnprice/toml-cli/releases and create a GitHub release for the tag.
  • Upload to that GitHub release the target/archive/toml-0.M.N-x86_64-linux.tar.gz file created by tools/build-release.

It would be nice to automate this so that it happens automatically when I push a tag to the repo, using GitHub Actions. This will be especially needed in the future when building macOS binaries (#22), as I'd otherwise have to go type commands on two different computers to build all the needed binaries.

One helpful model for how to do this is ripgrep. (I've already borrowed from other parts of their release-build scripting in writing tools/build-release.) Their GitHub workflow file for releases is here: https://github.com/BurntSushi/ripgrep/blob/master/.github/workflows/release.yml

There's also a draft version of this in #18 / #13.

@jankatins
Copy link

This is also a nice github action workflow for releasing (base don ripgrep, but a bit cleare in my opinion): https://github.com/mitsuhiko/rye/blob/main/.github/workflows/release.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants