[release] Split deployments into two actions #76
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.
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 pull request refactors the release workflow to separate PyPI and DockerHub deployments into distinct GitHub Actions workflows. The PyPI deployment is now handled in its own workflow, while DockerHub deployment has been moved to a dedicated workflow that can be triggered independently or as part of a coordinated deploy. Additionally, the process for extracting the project version from
pyproject.tomlhas been improved for better error handling.CI/CD Workflow Refactoring:
.github/workflows/deploy.ymlworkflow to coordinate deployments to both PyPI and DockerHub, using workflow dispatch and reusable workflow calls..github/workflows/dockerhub.yml, with improved steps for version extraction, Docker login, and image build/push..github/workflows/release.ymlto.github/workflows/pypi.ymland updated it to handle only the PyPI deployment, removing all DockerHub-related steps. [1] [2]Process Improvements:
pyproject.toml. [1] [2]