chore: fix corrupted v0.3.0 distro version to unblock the release - #50
Merged
Conversation
mwear
approved these changes
Aug 3, 2026
ocelotl
changed the title
This reverts commit 67b425d.
A leading 'v' (e.g. 'v0.3.0') passed to Prepare Release was written straight into version.py, producing an invalid PEP 440 version and the tag 'vv0.3.0', which broke CI and stalled the release. Validate the argument up front and fail before any file is written.
ocelotl
force-pushed
the
fix-release-v0.3.0-version
branch
from
August 3, 2026 22:35
9ec8f88 to
0539363
Compare
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
2 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.
Problem
The second
Prepare Releaserun was invoked with the version inputv0.3.0(leadingv) instead of0.3.0.scripts/bump_for_release.pydoesn't strip/validate the prefix, so commit67b425dset:packages/dash0-opentelemetry/.../version.py→__version__ = "v0.3.0"(invalid PEP 440), andv0.3.0 - 2026-08-03heading inCHANGELOG.rstabove the correct0.3.0section.This broke CI (
scripts-test→test_check_version_bumpedasserts each package version starts with a digit:AssertionError: ('dash0-opentelemetry', 'v0.3.0')) and the release never went out (nov0.3.0tag, noReleaserun, nothing on PyPI).Fix
Reverts
67b425d, restoring the correct prepared state from the first (good)Prepare Releaserun:version.py→0.3.00.3.0 - 2026-08-03section)Everything else from the good prepare (vendored
1.44.0.post1, cascaded==pins,uv.lock) is already correct and untouched. The failing test passes locally after this change.Follow-up (separate)
scripts/bump_for_release.pyshould reject/normalize a version argument with a leadingvso this can't recur.