-
Notifications
You must be signed in to change notification settings - Fork 20
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
feat: Integrate a release automation tool into the scaffolding release workflow #391
Comments
Just an FYI that there's a spike in the Holochain repo to investigate some release tooling options. This is one is one of the options but it'd be super if we converged on a single piece of tooling so we don't have to keep thinking about different tooling each time we go to a different repo. If we experiment with some tools before we converge that is also fine with me :) |
Yes, makes sense to use consistent release automation tooling. I suppose this is the issue you are currently using to track this? holochain/wind-tunnel#116 |
That's part of it yes, where we think that doing changelogs without custom tooling is likely going to work nicely with conventional commits. Hopefully a release tool would also use that. But the issue against the Holochain repo is this one holochain/holochain#4355. Not much detail yet, but the plan we've discussed verbally is to do a spike on tooling at some point |
Introduce
release-plz
or any other release automation tool into the release workflow. As well as keeping a changelog which will require enforcing conventional commitsThe text was updated successfully, but these errors were encountered: