chore(ci): automate releases #1427
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
2EEB
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an automated release
every weekonce a month + manual workflow if quick fixes are needed. I thought this would be a good compromise. I didn't want this on every push as otherwise all release notes just have only 1 PR entry and it's just really noisy. I see other people are also reconsidering that: renovatebot/renovate#9709.Also I just chose Monday so there's no Friday releases 🤣 but open to suggestions.
I tested this here (including all my derpy trial&error pushes):
https://github.com/nejch/python-gitlab-semantic-release
Resulting releases: https://github.com/nejch/python-gitlab-semantic-release/releases
testpypi package: https://test.pypi.org/project/python-gitlab/
changelog: https://github.com/nejch/python-gitlab-semantic-release/blob/master/CHANGELOG.md
I've also already set up the
PYPI_TOKEN
secret here.Initially I wasn't a fan of the auto-committed
CHANGELOG.md
but now I'm thinking it gives us a chance to consolidate the old changelog and release notes that are just sitting there since the GH Releases move. I can push another PR for that to add the old changes it to the new changelog.