Autils release process #26
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
|
Hi @clebergnu, thanks for your review. I have addressed your comments, please have a look. |
clebergnu
requested changes
Nov 27, 2024
There was a problem hiding this comment.
Actually, I caught an issue.
The "name" of the project (under pyproject.toml, [project]) needs to be lowercase "autils" too. Or else, the build process would generate:
Successfully built autils-0.1.dev47+gfa9c2de.tar.gz and Autils-0.1.dev47+gfa9c2de-py3-none-any.whl
Which I don't think it's intended.
Right, good catch. I will fix it. |
This commit creates pyproject.toml for configuration of packaging tools. This file contains basic information about Autils for deployment to PyPi and configuration for Autils build. The Autils use setuptools as build backend to ensure compatibility with Avocado. The build version is dynamic and based on git tags, it will make easier to automate build process during testing with test.pypi. Reference: #21 Signed-off-by: Jan Richter <[email protected]>
This is an introduction to pre-release and release wokflows. The pre-release will build the current main branch a upload it into TEST PyPi repo to test out the current build. The release workflow will generate new autils major or minor input based on the release. Then it will do the build and upload it to PyPi. Reference: #21 Signed-off-by: Jan Richter <[email protected]>
This commit adds automatic release triggering after the release voting has been successful. It will run the pre-release checks and if they pass it will do the release itself. Reference: #21 Signed-off-by: Jan Richter <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.
This PR introduces the release workflow for autils. The release workflow can be triggered manually, or it will be triggered by release-bot after successful voting. The release workflow supports a manual trigger for creating minor version releases, which can be used for security updates or critical fixes.
The PR also introduces pre-release workflow which uses
test.pypito run the dry-run of the release to check release process.Before the first release, we need to configure the
test.pypiandpypiinstances and create0.0tag to make this fully operational.Test of the release workflow:
https://github.com/richtja/autils/actions/runs/11840187779/job/32993407763
Test of the pre-release workflow:
https://github.com/richtja/autils/actions/runs/11841451279
Test of the release-bot:
https://github.com/richtja/autils/actions/runs/11856687960