Release Binaries on GitHub Releases

[jonaprieto]

As part of the Juvix-Geb integration, we require access to Geb binaries. Currently, we are able to generate the binaries manually, but for the convenience of our CI process, we would like to request that Geb be tagged and released on GitHub Releases. As soon as we get this, we'd also update the Juvix codespaces to provide Geb as part of the toolchain.

• Create a new release on GitHub Releases for each new version of Geb.
• Add, if possible, binaries for Ubuntu and macOS to each release.

PS.

For testing, one possible way to incorporate Geb in our GitHub CIs is something like this:

      - name: Install Geb binary
        uses: jonaprieto/action-install-gh-release@2
        with:
          repo: anoma/geb
          tag: latest
          binaries-location: bin # in case you put the binaries in a folder named `bin`
          cache: true

[rokopt]

@mariari Do you have an idea how we should do this?

[mariari]

@mariari Do you have an idea how we should do this?

Yeah we should cut release tags, and then do occasional releases, we really should stable our branches, so we aren't forking off main every time, but instead we should fork off a tag, and have certain tags symbolize release that we support.

We should discuss this at the retreat, as it covers general codebase health

[jonaprieto]

Do we have any progress on this issue? @mariari