Add release workflow

[Joffref]

Signed-off-by: Mathis Joffre [email protected]

Issue #, if available: #6 and #13

Description of changes: Add automatic publish of a binary release on tag creation that follows pattern : v*

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[austinvazquez]

Thanks @Joffref. LGTM.

[Kern--]

We're going to want release notes to go into the releases page. For firecracker-go-sdk, we have a CHANGELOG.md where we keep a running list of changes with a header for the version number. Maybe we could do the same here and parse out the set of changes to go in the release notes? (I think something simple like find the line that starts with # ${RELEASE_VERSION} and copy every line after that until the next line that starts with #.

That might be fine for a follow up PR, though.

[Joffref]

Knowing that there is at the moment no release file, I think it's more convenient to add this step to the workflow later in another PR to make it testable. What is your feeling about this ?

[alexellis]

We have that available and use it widely across all OpenFaaS projects and some of my own:

Have a look if the format is suitable for you? https://github.com/alexellis/arkade/releases

[Kern--]

I think that could be reduced to just the changes that would be visible to someone consuming the binary, but yes, something like that would work.

Let's defer that discussion for now. I think we can get one release out first and then worry about how to structure future release notes.

[alexellis]

SGTM @Kern-- - when do you expect to merge and release a binary?

We can then wind down https://github.com/alexellis/tc-tap-redirect-builder

[Kern--]

I'll merge this now. We have a little more process to follow than just pushing a tag today, so I'll get it going now to get this out ASAP.