You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we can agree to use conventional commits in this repo, then I think the best approach is to have two workflows:
Manually triggered release workflow, which uses release-plz to draft the GitHub release (including generating the change log from commit messages and tagging with the appropriate version tag), publish to crates.io, and bump the version.
Workflow triggered by publishing the GitHub release, which uses cargo-dist to build binaries, attach them to the release, and do other stuff like create homebrew formula (and hopefully conda recipe in the future).
Add a GitHub actions workflow for releasing that:
[(linux, mac) * (x86, arm)]
and attaches them to the GitHub releaseThe text was updated successfully, but these errors were encountered: