Repository navigation
Normalize release tags to vX.X.X format for python-semantic-release #569
Description
Activity
Tagged the 14 repos that have a real version history. Each new tag points at the same commit as the existing unprefixed tag, so PSR resolves to the version that is actually on PyPI.
Repo New tag Commit acid-block v0.4.1ad2eb138opaque-keys v4.0.0ae7f1353ccx-keys v2.0.2c3fe0b8cedx-enterprise-data v10.22.14b1bb7477openedx-chem v2.0.015489246enmerkar-underscore v2.4.1d220b9e1pytest-repo-health v4.0.0d219ba93taxonomy-connector v4.0.0e23cc187olxcleaner v0.3.0ad7bfd47codejail-includes v2.0.01615d644xblock-skill-tagging v1.0.0827ff4afopenedx-ledger v2.0.0a458d661edx-enterprise-subsidy-client v2.2.2430228bbenterprise-integrated-channels v0.1.707bbc52f8Four repos are dropped from the list.
web-fragmentsandxblock-free-text-responseare archived, so they cannot be pushed to and are not PSR conversion candidates.license-managerandopenedx-webhookshave no version tags at all; theirs are deployment markers likerelease/verawood.1andrelease-2023-11-27, and both declareversion = "0.1.0"inpyproject.toml. There is no earlier version for PSR to miss in those two, so starting at 0.1.0 is the right answer rather than a bug.Two corrections to the list.
enterprise-integrated-channelsis at 0.1.70, not 0.1.69; 0.1.70 went out 2026-09-11.acid-blockgotv0.4.1rather thanv0.4.0, becauseacid/__init__.pyatad2eb138, the commit the0.4.0tag points at, reads__version__ = '0.4.1'and PyPI hasacid-xblock 0.4.1from 2024-10-01 with no matching tag. Taggingv0.4.0there would have let PSR compute 0.4.1 next and collide with what is already published.Five publish workflows fired and failed, which is expected. ccx-keys, edx-enterprise-data, openedx-chem, enmerkar-underscore and pytest-repo-health run
pypi-publish.ymlonpush: tags: - '*', so each tag built the already-released version and got400 File already existsback from PyPI. Nothing was published, and every dist still shows its original version and upload date. Those workflows get replaced byrelease.ymlas each repo converts.One thing to watch at conversion time:
openedx-chemdeclares 2.0.1 inchem/__init__.pyandcodejail-includeshardcodes 3.0.0 insetup.py, but the last release of each is 2.0.0. PSR computes the next version from commit messages offv2.0.0, so those hand-written numbers will be ignored.Verified 2026-09-23.
Reacted by Muhammad Farhan Khan
Purpose
Normalize the release/version tag format to
vX.X.X(with thevprefix) across the repos listed below.Why this is needed
As we convert repos to python-semantic-release (PSR), PSR looks at existing tags to determine the current version and compute the next one. PSR expects tags in the form
v#.#.#, but several repos currently tag versions without thevprefix (e.g.4.0.0instead ofv4.0.0).When the
vprefix is missing, PSR fails to recognize the latest version and wrongly starts a fresh0.1.0release instead of bumping from the real current version. Re-tagging these repos to thevX.X.Xformat ensures PSR picks up the correct history and versions the next release accurately.Slack message
Repos to fix
These repos have their latest release/version tag without the
vprefix:0.4.0->v0.4.1(the0.4.0tag ships 0.4.1)4.0.0->v4.0.0openedx-webhooks- no version tags,release-2023-11-27is a deployment marker; not applicable2.0.2->v2.0.2web-fragments- archived; not applicable10.22.14->v10.22.142.0.0->v2.0.0xblock-free-text-response- archived; not applicable2.4.1->v2.4.14.0.0->v4.0.0license-manager- no version tags,release/verawood.1is a deployment marker; not applicable4.0.0->v4.0.00.3.0->v0.3.02.0.0->v2.0.01.0.0->v1.0.02.0.0->v2.0.02.2.2->v2.2.20.1.70->v0.1.70(was listed as 0.1.69)Parent: #506