adding pypi upload and versionning #39
Merged
Conversation
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.
This pull request introduces a workflow for publishing the project to PyPI and integrates
setuptools_scmfor automated version management. The most important changes include adding a GitHub Actions workflow for PyPI publishing, updating thepyproject.tomlfile to usesetuptools_scm, and configuring version fallback behavior.Workflow for PyPI Publishing:
.github/workflows/publish-pypi.yml: Added a GitHub Actions workflow to publish the project to PyPI when a version tag is pushed. This includes steps for setting up Python, building the package, verifying the version matches the tag, and publishing to PyPI using OIDC trusted publishing.Version Management with
setuptools_scm:pyproject.toml: Updated build requirements to includesetuptools_scmfor dynamic versioning based on Git tags. Removed the hardcodedversionfield and replaced it with adynamicversion field.pyproject.toml: Added a[tool.setuptools_scm]section to configuresetuptools_scm, including a fallback version (0.1.dev0) to use when no tags are present.