-
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
Automate releases #575
Comments
So the current iteration isn't fully automatic
|
That could be automatized with https://github.com/gradle-nexus/publish-plugin/ |
Oh right, thanks, I was hoping for a little human intervention on purpose at first. I think @vlsi release plugin does automation as well? |
Most likely yes. As Visi is closer to this project, probably his plugin will be "better supported" here. |
Sure, that's a good idea to verify the things. Btw, in some projects (e.g. the Apache projects), people close the staging repository, giving the others chance to test it manually, verify content, etc. And once it is done, the staging repository can be released (manually or from a manual step in the pipeline). Of course, sigstore-java might not need that - e.g. having a good test harness and some other verifications in place. I know many project which release automatically from tag (or from |
Yeah I agree. We're a little immature in release right now. Will work on a better mechanism. I don't have a preference on release plugin. So either is fine. |
Gradle:
Maven-Central:
The text was updated successfully, but these errors were encountered: