fix(#868k5bbdr): Read version from PKG-INFO when packageVersion env var is absent#7
Merged
Conversation
Build tools like uv re-run setup.py at install time without the packageVersion env var, causing the version to fall back to 4.15.0 instead of the published version. This makes uv's metadata check fail: "Package metadata version 4.15.0 does not match given version X.Y.Z". Fall back to reading PKG-INFO (present in the extracted sdist root) so any build tool gets the correct version without needing packageVersion. Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
vavsab
changed the title
loopingrage
approved these changes
Jul 7, 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
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
Build tools like uv re-run
setup.pyat install time without thepackageVersionenv var set. This causesabout.pyto fall back to4.15.0, making uv's metadata consistency check fail:Poetry avoids this because it trusts the
PKG-INFOalready embedded in the tarball. uv (and pip 24+) re-evaluatesetup.pyand catch the mismatch.Fix
When
packageVersionis absent, fall back to reading theVersionfield fromPKG-INFOin the sdist root. That file is always present in the extracted sdist and contains the correct published version.Affected packages
botbuilder-core-forkedbotbuilder-integration-aiohttp-forkedbotframework-connector-forkedbotframework-streaming-forkedAfter merge
Once the new version is published to fury, remove the
packageVersion=1.0.21workaround from mappedgpt-bot Dockerfile and the[[tool.uv.dependency-metadata]]entries from pyproject.toml.🤖 Generated with Claude Code