ci: force local wheels via uv override in cross-tests#1723
Conversation
There was a problem hiding this comment.
Pull request overview
This PR updates the downstream cross-test GitHub Actions workflows to force the freshly built local uipath-* wheels into uipath-langchain-python and uipath-integrations-python via a uv override mechanism, avoiding resolution failures caused solely by downstream version caps during backward-compatible minor bumps.
Changes:
- Replaces
uv add ../wheels/.../*.whlwith a step that generates an overrides file pointing at local wheel URIs and exports it viaGITHUB_ENV. - Applies the same override injection pattern across both unit-test and integration-test jobs for each downstream repo.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| .github/workflows/test-uipath-langchain.yml | Generates and exports a uv overrides file to force local wheels for langchain cross-tests (unit + integration jobs). |
| .github/workflows/test-uipath-integrations.yml | Generates and exports a uv overrides file to force local wheels for integrations cross-tests (per-package tests + integration jobs). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
63abe2b to
f122aa2
Compare
|
🚨 Heads up:
|



Summary
uipath-langchain,uipath-integrations) now inject the freshly built wheels via uvoverride-dependenciesinstead ofuv add, so a backward-compatible minor bump in uipath-python no longer fails the cross-test purely on the downstream version capWhy
a minor bump (e.g. uipath 2.10 -> 2.11) is outside the downstream
<2.11.0cap, souv addof the new wheel hits an unsatisfiable resolve and the cross-test fails before testing anything real. overriding decouples the cross-test from the pin while still running the actual new code.