fix: install uv on the runner so the API build works in CI - #7
Merged
Conversation
`vercel build` failed with "uv is required but was not found in PATH". Vercel's Python runtime builds with uv rather than pip -- which is also why the API declares its dependencies as a uv workspace in the root pyproject.toml -- and GitHub runners do not ship it. It worked locally only because uv happened to be installed on that machine, so the manual first deploy gave no warning. Only the API job needs it; the web project builds with Node. The two failures before this one are now behind us: the Vercel token had to be scoped to the team rather than a personal account, and the migrate job has since run green against Neon.
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.
Deploy API (production)fails onmainwith:Vercel's Python runtime builds with uv, not pip — the same reason the API declares its dependencies as a uv workspace in the root
pyproject.toml— and GitHub runners don't ship it. My manual first deploy gave no warning because uv happened to already be installed on that machine.Adds
astral-sh/setup-uv@v6to thedeploy-apijob only;deploy-webbuilds with Node and doesn't need it.Where the pipeline stands
Each failure so far has been one step further along, which is what you'd expect from a first run:
vercel pullvercel pullvercel buildCheck deploy secrets,test, andalembic upgrade headare all green now, and the migration has run successfully against Neon.