Automate releases using python-semantic-release #2068
Open
dikshaa2909 wants to merge 1 commit intoaboutcode-org:mainfrom
Open
Automate releases using python-semantic-release #2068dikshaa2909 wants to merge 1 commit intoaboutcode-org:mainfrom
dikshaa2909 wants to merge 1 commit intoaboutcode-org:mainfrom
Conversation
Signed-off-by: dikshaa2909 <dikshadeware@gmail.com>
This file contains hidden or 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
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.
Automate Releases using python-semantic-release
Fixes #1992
This PR introduces an automated, CI-driven release workflow using
python-semantic-release to remove the remaining manual steps
(version bumping and tagging) from the current release process.
Technical approach
pyproject.tomlscancodeio/__init__.pyCHANGELOG.rstvX.Y.ZGit tag on merge tomainImplementation
The goal is to make releases:
No changes were made to the current PyPI workflow logic — this proposal
strictly automates the versioning and tagging layer.
This implementation is intentionally minimal and scoped, and can be
adjusted (tooling, branching model, changelog behavior) based on
maintainer preference.