Adds automated flexible changelog generation and release builds with pre-built binaries.

IEEE-VIT / templa-rs

One-Stop Solution for all boilerplate needs!

MIT License

28 stars 22 forks source link

Adds automated flexible changelog generation and release builds with pre-built binaries. #31

Closed Animeshz closed 3 years ago

Animeshz commented 3 years ago

Summary:

Changelog matching using regex as in .github/chglog/release.yml, currently matched for current type feat: something, can also process feat(subtopic): something as well, subtopic will appear bold if present in the changelogs.
Release template based on simple markdown file completely flexible, present at .github/chglog/RELEASE.tpl.md
Added workflow that builds on variety of platforms as here .github/workflows/release.yml

Sample tested action Release output

^ made using the following cmds

git tag v0.0.9
git push origin v0.0.9

Notes: made it failsafe so should release those builds where atleast one of platform is able to build, and build fails should be available at actions section to monitor any.

Animeshz commented 3 years ago

Fix #8

mintbomb27 commented 3 years ago

Hey @Animeshz ! Thanks a lot for your contribution! We'll be reviewing your PR very soon!

ShubhamPalriwala commented 3 years ago

Hey @Animeshz, how can one verify the SHA256 that is generated as an artifact with the image?

Animeshz commented 3 years ago

@ShubhamPalriwala You can do something like this:

curl -LO https://link/to/file
sha256sum file
curl -L https://link/to/file.sha256

You can also use the automated check sha256sum provide by passing sum and file by pipe

curl -LO https://link/to/file
echo "$(curl -L https://link/to/file.sha256) file" | sha256sum --check

Animeshz commented 3 years ago

Any updates 👀

ShubhamPalriwala commented 3 years ago

Okay this is valid but an easier way to verify a file is using cosign. For this PR, let's just have a release and changelog generation! The signing of images is already a separate issue opened in #6 using cosign

Animeshz commented 3 years ago

Okay, I'll remove that in a bit 👍

Animeshz commented 3 years ago

@Mannan-Goyal Put in the notes in topmost comment:

Notes: made it failsafe so should release those builds where atleast one of platform is able to build, and build fails should be available at actions section to monitor any.

Edit: Do we want the opposite behavior??

mintbomb27 commented 3 years ago

@Animeshz Yes! We do expect the opposite behaviour. If any of the build fails, the whole release shouldn't happen.