Verify Python package version number changes via GitHub action#430
Merged
Verify Python package version number changes via GitHub action#430
Conversation
vcschapp
force-pushed
the
pypi-publish-check-versions-gh-action
branch
from
a87ac86 to
3f16f08
Compare
vcschapp
added
change type - cosmetic 🌹
vcschapp
requested review from
RoelBollens-TomTom,
jenningsanderson,
mojodna and
sasastanojkov
mojodna
previously approved these changes
Jan 30, 2026
OvertureMaps/schema-wg#406 This commit adds a GitHub action that runs whenever an `__about__.py` or `pyproject.toml` file gets changed. WHAT THE ACTION DOES -------------------- - Identify any packages with changed version numbers. - Verify that that version number doesn't already exist in PyPI.* WHAT THE ACTION DOES NOT DO --------------------------- - It does not verify that the version number is a valid semantic version (semver) because this validation is now done by `$ make check` and `$ make check-versions` in `Makefile`. WHY WE WANT THIS BEHAVIOR ------------------------- - The purpose of this GitHub Actions workflow is to give us confidence that we are catching invalid version numbers, including attempts to re-publish to an existing version number, at the stage when the PR is drafted, rather than finding out later when it has been merged and our (soon to be written) publish automation kicks in. * For now, the PyPI repository is the Overture-run one. Later, when we're ready to release, we'll point ourselves at public PyPI.
vcschapp
force-pushed
the
pypi-publish-check-versions-gh-action
branch
from
3f16f08 to
1ba206f
Compare
jenningsanderson
approved these changes
Jan 30, 2026
RoelBollens-TomTom
approved these changes
Jan 30, 2026
sasastanojkov
approved these changes
Jan 30, 2026
This was referenced Jan 30, 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
5 participants
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.
Main Change
Adds the PR validation branch of the sequence diagram found on 2026-01-28 / CODING SESH 💻. This is a GitHub action that runs whenever an
__about.py__orpyproject.tomlfile gets changed.What the action does do
What the action does not do
$ make checkand$ make check-versionsinMakefile.Why we want this
The purpose of this GitHub Actions workflow is to give us confidence that we are catching invalid version numbers, including attempts to re-publish to an existing version number, at the stage when the PR is drafted, rather than finding out later when it has been merged and our (soon to be written) publish automation kicks in.
† For now, the PyPI repository is the Overture-run one. Later, when we're ready to release, we'll point ourselves at public PyPI.
Ancillary Changes
$ make checkvalidation on commit push tomainanddevbranches, not just on PR.Testing
Tested as much as possible locally, but ultimately we have to run it on GitHub to ensure the actions work right.