Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

(feat): full release automation #1655

Open
ilan-gold opened this issue Sep 4, 2024 · 0 comments
Open

(feat): full release automation #1655

ilan-gold opened this issue Sep 4, 2024 · 0 comments
Assignees

Comments

@ilan-gold
Copy link
Contributor

Please describe your wishes and possible alternatives to achieve the desired result.

In the wake of our first "automated" changelog generation, I think we can automate the rest of the process as follows:

  1. On merge from a branch called release_notes_X.Y.Z.xcxc into either a version or the main branch, we generate a github release either based off the newest changelog notes or the release_notes_X.Y.Z.xcxc branch name
  2. Our normal release process proceeds

This the trigger for release would be hatch run towncrier:build X.Y.Z.xcxc

@ilan-gold ilan-gold self-assigned this Sep 4, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant