Change package version field to dynamic - #118
Merged
C-Achard merged 5 commits intoAug 24, 2026
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Update `pyproject.toml` to use dynamic versioning by adding `setuptools_scm[simple]` to build requirements and replacing the hardcoded project version with `dynamic = ["version"]`. This moves version management to SCM tags instead of a manually maintained value.
Set `fetch-depth: 0` on the checkout step in `.github/workflows/python-package.yml` so the workflow has complete git history when running against release tags (including `workflow_dispatch` tag refs). This avoids shallow-clone limitations in downstream release/versioning steps.
Copy link
Copy Markdown
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the Python packaging configuration so the published package version is derived from the Git tag (GitHub release tag) instead of being manually maintained in pyproject.toml, streamlining the release process.
Changes:
- Switch project version metadata to dynamic = ["version"] and add setuptools-scm as a build dependency.
- Update the CI checkout step to fetch full git history (to support SCM-derived versioning during builds).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| pyproject.toml | Removes the static version field and enables dynamic versioning via setuptools-scm in build requirements. |
| .github/workflows/python-package.yml | Adjusts checkout depth to ensure git metadata is available for SCM-based version computation during CI builds. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Sorry, something went wrong.
Comment thread
.github/workflows/python-package.yml
deruyter92
approved these changes
Aug 24, 2026
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.
The version tag from the GitHub release should be the authority on version release.
This avoids having to manually bump the release number in pyproject and helps streamline the release process.