Draft
Conversation
Pin setup-uv to 0.11.0 in CI so we can test whether the Python\nbuild failure tracks the uv upgrade.\n\nSplit CI into separate test, example, and build jobs so the Ruby\nexample failure cannot mask the package build result in the same run.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Revert the investigation workflow split so this branch matches the\nmain CI job structure while keeping the uv pin in place.
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
1 participant
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.
Goal
Pin
uvback to0.11.0and leave Bundler unpinned to test whether the Python build failure tracks theuvupgrade.What changed
astral-sh/setup-uv@v3toversion: 0.11.0lint-and-tests,example-tests, andbuild-packagejobs so the Ruby example failure cannot mask the build resultExpected interpretation
build-packagepasses andexample-testsstill fails, that supportsuvdrift as the Python-side cause and an independent Ruby-side issueuvupgrade alone is probably not sufficient to explain the Python regression