chore+ci: bump version to 0.3.0 and pin official build toolchain - #1268
Merged
Conversation
timenick
approved these changes
Aug 3, 2026
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
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
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.
Release-window changes needed to build a correct v0.3.0 wheel.
chore(release): bump version to 0.3.0(+ uv.lock sync)Bumps
pyproject.toml(anduv.lock) to0.3.0. Version is exposed at runtime viaimportlib.metadata, sopyproject.tomlis the only source.ci(release): pin official build toolchain versionsModelKit Official Buildinstalled its toolchain withpip install --upgrade build twine packaging— completely unpinned.build1.5.1 (released since v0.2.0) breaks the build inside the OneBranch container:The sdist step fails and the wheel step is skipped, so the build produces nothing. Verified on run 153739315 (failed,
build1.5.1) vs 150550609 (v0.2.0, succeeded,build1.5.0).build1.5.0 and 1.5.1 have identical_pip_env(), so this is environment behavior in 1.5.1, not a change on our side.Pinning to the versions that produced v0.2.0 restores a green build and, more importantly, stops a third-party release from breaking the release build on publish day.
Validated: official build 153740145 succeeded on this branch — sdist, wheel, iKey verification, and PyPI validation all green.