fix: Update semantic-release configuration for consistency and correct versioning #38
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.
Summary
This PR addresses configuration inconsistencies and improves the semantic-release setup for the
early-stopping-pytorch
package. Changes were made to ensure proper versioning, tagging, and build process alignment, which should eliminate the warnings seen in recent CI runs.Changes Made:
Updated
pyproject.toml
:version_variable
to match the actual package path.tag_format
under[tool.semantic_release]
.version_toml
to synchronize version updates withpyproject.toml
.upload_to_pypi
tofalse
for now, as per project requirements.Workflow Update (
.github/workflows/release.yml
):contents: write
for better security.workflow_dispatch
trigger for manual release control.Rationale
These changes ensure that versioning is consistently managed and that warnings are minimized, improving CI/CD pipeline efficiency. The configuration should now support smoother releases with semantic versioning and prevent potential issues with incorrect tag formats or misconfigured variables.