could you create releases?

[deknos]

Hi,
i am using a tool called binenv (https://github.com/devops-works/binenv) it basically manages and download binaries from github which are in its cache and have releases. it would be really cool if you could create releases, then you get instantly a tool which manages versions and installs it on systems :)

[FiloSottile]

A tagged release would also be useful for moving the version in Homebrew off v0.6.0 which is two years old and doesn't build with Go 1.16 anymore (because it was not a module), and to install with modules-aware go install which will also prefer tags to master.

[geeseven]

@deknos,

I am not sure if you are asking for new version to get tagged and released or if you are looking for this repository to use GitHub's releases feature. If it is the later, this repository already uses releases. While I am not familiar with binenv, I think it could support gron as is.

[Moisan]

On the Homebrew side, the issue is also that all gron releases are tagged as pre-releases currently. If the releases aren't meant to be stable, then that changes how we would handle the packaging: we would remove the package from homebrew-core. Otherwise, tagging them as simply "release" would make more sense.

[SMillerDev]

I'd like to point out that github pre-releases are generally understood to be supplemental to semver. If eg a 0.6 version is unstable compared to 0.5 that specific version might need to be pre-release. But if the whole project hasn't reached 1.0 stability yet tagging all of them as pre-release makes it unclear for users IMHO.

[chenrui333]

cc @tomnomnom

[spitlo]

Another issue with pre-releases is that they don’t show up in the Github API, making it hard to programatically fetch the latest version for scripts that might want to do that. For example, I have a script I use to keep a few tools updated on my different environments. It uses the /releases/latest endpoint to know what version to download, but for this project, the corresponding url returns a 404.