fix(deps): move the uipath-runtime range to 0.13 on the 0.0.84 line - #130
Merged
radu-mocanu merged 2 commits intoSep 1, 2026
Merged
Conversation
Releases 0.0.84.post1 with 0.0.84's source and two dependency ranges moved: - uipath-runtime: >=0.12.1,<0.13.0 -> >=0.13.0,<0.14.0 - uipath: >=2.13.0,<2.14.0 -> >=2.13.23,<2.14.0 0.0.84 caps uipath-runtime below 0.13.0 and 0.0.85 raised the uipath floor to 2.14.1, so a consumer on the uipath 2.13 line has no published uipath-dev that admits uipath-runtime 0.13.x. The uipath floor moves to 2.13.23 because that is the only release on the 2.13 line admitting it. Both ranges stay within a single minor. Source is unchanged and the test suite passes against uipath-runtime 0.13.2. Cut from 93fe8f5, the commit that built 0.0.84. 0.0.85 already exists, so this is a post-release rather than a patch increment. uv.lock is not regenerated here: uipath 2.13.23 is not on PyPI yet.
uipath 2.13.23 is published, so the lock resolves. Pinned at uipath-runtime 0.13.2 so CI exercises the runtime this release is cut for.
radu-mocanu
marked this pull request as ready for review
September 1, 2026 11:11
Collaborator
Author
|
Undrafted — ready to merge and dispatch. |
ionut-mihalache-uipath
approved these changes
Sep 1, 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.
Releases
uipath-dev0.0.84.post1: 0.0.84's source with two dependency ranges moved.Draft until
uipath2.13.23 is published (UiPath/uipath-python#1878).uv.lockis intentionally not regenerated here, becauseuv lockcannot resolve against a version that does not exist yet.Why
There is a gap for anyone on the
uipath2.13 line who needsuipath-runtime0.13.x: 0.0.84 caps the runtime below 0.13.0, and 0.0.85 lifted that cap but raised theuipathfloor to 2.14.1 in the same release. So 0.0.84 excludes the runtime and 0.0.85 excludes the SDK, and no publisheduipath-devfits.This closes the gap on the 0.0.84 line. The
uipathfloor moves to 2.13.23 because that is the only release on the 2.13 line that admitsuipath-runtime0.13.x.Since
uipath-devsits in consumers' dev groups, the gap blocksuv lockeven though the tool never ships in their wheel.Both ranges move rather than widen, so each stays within a single minor.
Compatibility
The source is unchanged from 0.0.84 and its test suite passes against
uipath-runtime0.13.2, 21 passed.Branch
Cut from
93fe8f5, the commit that built 0.0.84, per the open-source hotfix procedure. Base branchrelease/uipath-dev-0.0.84is that same commit. Not formain.Versioning
0.0.85 already exists, so this is a post-release of the version being fixed rather than a patch increment. PEP 440 orders it
0.0.84 < 0.0.84.post1 < 0.0.85, so it does not supersede 0.0.85 for anyone already on it.Sequencing
uipath2.13.23 (fix(deps): move the uipath-runtime range to 0.13 on the 2.13 line uipath-python#1878)uv lockhere, push the lockfile, undraft, merge