-
Notifications
You must be signed in to change notification settings - Fork 73
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make releases EZ #279
Make releases EZ #279
Conversation
- make changelog _actually_ follow https://keepachangelog.com/en/1.0.0/ to a T - create release workflow which automates creating binaries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look good from what I understand; just a question about how the changelog reader knows how to get the version. Is there a way to test without actually merging to the release branch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One minor thing found.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks cool.
Co-authored-by: Tarik Gul <47201679+TarikGul@users.noreply.github.com>
PR adds a github action workflow which automates releases. It will run whenever the branch
release
gets pushed to. Once it's pushed to, the workflow:polkadot-archive
in--release
, packages binary in.deb
and also standalone linux (as with all previous releases)This PR also fixes CHANGELOG to follow keep a changelog, and creates a separate CHANGELOG for polkadot-archive. This will make it easier to update in the future I think.
This won't publish the release, but it will create a draft that we can look over and modify and then publish from Github UI. This is my preferred way, just because it forces double-checking things, but I'm open to other opinions
I suspect this could further be automated by adding a
diener
step to automatically change all substrate/polkadot refs to the latest release with some more github-action magic.I was testing this stuff out earlier in a personal repo before creating the action (Release branch): https://github.com/insipx/test-gh-action