Skip to content
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

Open
wants to merge 20 commits into
base: master
Choose a base branch
from

Conversation

AlejandroCabeza
Copy link
Contributor

@AlejandroCabeza AlejandroCabeza commented Jan 29, 2025

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:

  • 1. Description added.
  • 2. Context and links to Specification document(s) added.
  • 3. Main contact(s) (developers and specification authors) added
  • 4. Implementation and Specification are 100% in sync including changes. This is critical.
  • 5. Link PR to a specific milestone.

@AlejandroCabeza AlejandroCabeza added this to the Iteration 9 milestone Jan 29, 2025
@AlejandroCabeza AlejandroCabeza self-assigned this Jan 29, 2025
@danielSanchezQ danielSanchezQ linked an issue Jan 29, 2025 that may be closed by this pull request
9 tasks
@danielSanchezQ danielSanchezQ removed a link to an issue Jan 29, 2025
9 tasks
@danielSanchezQ danielSanchezQ linked an issue Jan 29, 2025 that may be closed by this pull request
@AlejandroCabeza AlejandroCabeza marked this pull request as ready for review January 30, 2025 11:42
Comment on lines +179 to +187
## 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
Copy link
Contributor

@youngjoon-lee youngjoon-lee Jan 31, 2025

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?

Copy link
Contributor Author

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).

Copy link
Collaborator

@danielSanchezQ danielSanchezQ left a 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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Packaging and Distribution] Create release
3 participants