-
Notifications
You must be signed in to change notification settings - Fork 21
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
feature(ci): Nomos Node release page #1005
base: master
Are you sure you want to change the base?
Conversation
## Checklist | ||
Before publishing please ensure: | ||
- [ ] Description is complete | ||
- [ ] Changelog is correct | ||
- [ ] Assets for all platforms exist | ||
- [ ] Pre-release is checked if necessary | ||
- [ ] Remove this checklist before publishing the release. | ||
draft: true | ||
prerelease: true |
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.
This checklist is for reminding us of a final check just before removing the prerelease
badge?
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.
Actually, that'd be the draft
; but yes.
prerelease
should be set to false
, I believe, as it's intended to mark a beta
or alpha
release (or the likes of).
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.
Thanks for the effort
1. What does this PR implement?
Release page for Nomos Node. Produces a release page from a hardcoded template and attaches the bundled binaries.
There's still room for improvement although that's left for a future iteration. If you want to double check what's remaining of this task, please check this issue.
A draft release page has been produced by this workflow. You can check it in the releases page or go to the specific release.
Closes: #1002
2. Does the code have enough context to be clearly understood?
Yes
3. Who are the specification authors and who is accountable for this PR?
N/A
4. Is the specification accurate and complete?
N/A
5. Does the implementation introduce changes in the specification?
No
Checklist
Warning
Do not merge the PR if any of the following is missing: