I made a for which enables you to tag for a release and the workflow will set your project.cabal to the version specified by the tag, make a commit that moves the tag to that new commit, and make a release for that tag which includes a static binary that is in a tar.gz.

Speaking of which, here's the first release of (an alpha) which was built with that system:

Hm, maybe having it make a commit/move tag for changing the project.cabal version is a bad idea and instead I should have it detect new versions when a commit changes the version in the cabal file and it can tag the release for me. Rebasing is annoying and so are those tag errors.

Sign in to participate in the conversation

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.