-
Notifications
You must be signed in to change notification settings - Fork 6
DEVP-650: Fix PyPI version control to resolve conflicts #50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
DEVP-650: Fix PyPI version control to resolve conflicts #50
Conversation
- Replace GitHub run_number with hatch version for test deployments - Remove SETUPTOOLS_SCM_PRETEND_VERSION override - Use git-based semantic versioning from hatch-vcs - Require exact git tags for production releases Resolves version inconsistencies between local and PyPI deployments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Updates the PyPI publishing workflow to use hatch/hatch-vcs-based versioning for test builds and to enforce tag-only versioning for production releases, addressing version conflicts between local builds and published artifacts.
Changes:
- Use
hatch versionfor test deployments instead of appendinggithub.run_number. - Remove
SETUPTOOLS_SCM_PRETEND_VERSIONoverride logic. - Enforce production releases to run only when the commit has an exact git tag.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@cmworkato can you take a look at copilot's comments and resolve or fix? |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Resolves version inconsistencies between local and PyPI deployments.