-
Notifications
You must be signed in to change notification settings - Fork 22
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
Update the release process and use GitHub Attestations #127
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #127 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 1 1
Lines 96 96
======================================
Misses 96 96 ☔ View full report in Codecov by Sentry. |
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 PR!
This looks good to my unpracticed build systems eye, and the docs are great 🫶
push: | ||
tags: | ||
- '*-?v[0-9]+*' | ||
- '**[0-9]+.[0-9]+.[0-9]+*' |
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.
Reasoning for removing the v
prefix - unnecessary with a better regex to identify the tag?
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.
So this whole action is generated with cargo-dist completely now.
They did this to make the regex more permissive for things some other projects liked using for release tags. Doesn't affect us though :)
See axodotdev/cargo-dist@55a74ce if you are curious!
Now that cargo-dist has an option for enabling GitHub attestations we're going to switch to using it as-is and reduce some of the manual effort in the release process.
23df6b5
to
0144925
Compare
|
@orbitalturtle 👋 Just letting you have a chance to look over the more streamlined release process and give any feedback :) I believe it's all in order and should make releases a breeze. |
@dunxen Amazing! 🎊 Sorry I've been slow to take a look. I'll plan to do a run through this week :) |
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 good to me! Thanks for adding the detailed instructions in MAINTAINERS.md; I'm excited to give this a try for LNDK v2.
Fixes #38.