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

Create RELEASE.md #292

Merged
merged 2 commits into from
Oct 13, 2021
Merged

Create RELEASE.md #292

merged 2 commits into from
Oct 13, 2021

Conversation

metalmatze
Copy link
Member

Create a RELEASE.md.
I'm currently following this guide to release v0.1.1.

@CLAassistant
Copy link

CLAassistant commented Oct 12, 2021

CLA assistant check
All committers have signed the CLA.


Tag the new release with a tag named `v<major>.<minor>.<patch>`, e.g. `v2.1.3`. Note the `v` prefix. You can do the tagging on the commandline:

```bash
Copy link
Member

@brancz brancz Oct 12, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not against this, but I think it's worth calling out that this entire flow can be done from the GitHub UI as well:

  • Create branch
  • Create release, and tag at the same time

Since our artifacts are 100% reproducible, signing the tag is a nice gesture, but doesn't really provide an additional security benefit.

FWIW I've done the releases I've done entirely through the UI.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wow. Nice. I wasn't even going to try that, but just did for v0.1.1
That's such a low bar for creating a release. 👏
I'll update this doc, if it all worked out fine 😊

@metalmatze metalmatze merged commit 70cfc09 into main Oct 13, 2021
@metalmatze metalmatze deleted the RELEASE.md branch October 27, 2021 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants