You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Introduce release-plz or any other release automation tool into the release workflow. As well as keeping a changelog which will require enforcing conventional commits
The text was updated successfully, but these errors were encountered:
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 :)
c12i
changed the title
feat: Integrate release_plz into the scaffolding release workflow
feat: Integrate a release tool into the scaffolding release workflow
Oct 22, 2024
c12i
changed the title
feat: Integrate a release tool into the scaffolding release workflow
feat: Integrate a release automation tool into the scaffolding release workflow
Oct 22, 2024
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: