Create releases

[ngerakines]

This is a feature request to improve developer experience.

GitHub releases would be a great place to have change log information, as well as zstd dictionaries. Using them would accomplish a couple of things:

• Migrate the project to a formal tag-and-release cycle where people can see what the latest deployed changes are and subscribe to updates.
• Allow the zstd_dictionary to be moved out of the repository and attached to releases as blob attachments
• Move downloading release content (builds and artifacts like the zstd_dictionary) onto the releases CDN and out of git

[ericvolp12]

TBH I've never really maintained a project using that formal of a flow and I'm not totally sure what the process for doing releases is there. I don't anticipate there being a ton of change momentum on this project soon considering it's a pretty simple interface but I do see the appeal of having some form of versioning.

[uniphil]

it would be nice to have a quick place to find about breaking changes like #7 when i only notice my thing isn't working a few days later :) (realizing this is only a problem for me because i'm relying on the free public hosted instances, not complaining)

if you are thinking of adopting something this way, github does a few nice things automatically if you make tags and connect them to their "releases" through the web UI. Or, a classic changelog file avoids github lock-in for a bit of manual (and/or scripted*) work.

*git log changes since last tag

i use this on a few projects to generate changelogs, but usually manually edit emails to github ids and sometimes linking PRs before committing. there are probably better ways.

git log --pretty=format:'- %s (%ae)' $(git describe --tags --abbrev=0)..

just as example