build(bootstrap): manage uv with mise by marcusds · Pull Request #1134 · NVIDIA-NeMo/nemo-platform

marcusds · 2026-08-06T19:09:19Z

Summary

Extends the mise-managed toolchain from #1109 to cover uv.

pyproject.toml requires uv>=0.9.14,<0.10.0, but nothing installed a matching uv — README.md pinned an installer URL and AGENTS.md told Cursor Cloud users to pip install 'uv>=0.9.14,<0.10.0' after hitting the mismatch. Same gap mise already closes for Node.js and pnpm.

Pin uv = "0.9" in mise.toml. Resolves to 0.9.30, inside the required-version range, and mise verifies GitHub artifact attestations plus a checksum on install.
Add UV := $(MISE_EXEC) uv and route all 48 uv invocations in the Makefile through it, so make bootstrap-python, make test-unit, make update-sdk and the rest use the pinned uv regardless of PATH. NMP_SKIP_MISE=1 still falls back to bare uv.
verify-python-version and bootstrap-python now depend on verify-mise.
Default PYTHON_VERSION to 3.12. It was 3.11, which no longer satisfies requires-python = ">=3.12,<3.15", so uv python install fetched an interpreter the project can't use while uv venv silently picked a different one.
Reuse a GITHUB_TOKEN from the environment or the gh CLI during mise install, and explain the GitHub rate limit on failure instead of surfacing a bare 403.
Set NMP_SKIP_MISE=1 for the CI workflow, which provisions its own toolchain. Detail below.
Document the bootstrap ordering in SETUP.md, and drop the now-obsolete pip install 'uv>=0.9.14,<0.10.0' advice from AGENTS.md and the uv prerequisite from README.md's source-checkout path.

Global uv version mismatches

This also fixes the case where uv is already installed globally at a version outside required-version. AGENTS.md documents the symptom today — uv 0.11.x fails uv sync with a version mismatch, and the advised fix is to downgrade the machine-wide install, which breaks other projects.

Because every uv invocation goes through mise exec --, the mise-managed uv takes precedence over whatever is first on PATH, so no downgrade is needed. Verified with a stub uv reporting 0.11.7 ahead of everything on PATH:

$ command -v uv
/tmp/fakebin/uv
$ uv --version
uv 0.11.7 (STUB - wrong version)

$ make verify-python-version
"…/mise" exec -- uv python find 3.12
→ …/cpython-3.12.12-macos-aarch64-none/bin/python3.12      # mise's uv used

$ make verify-python-version NMP_SKIP_MISE=1
STUB uv called with: python find 3.12                       # opt-out uses PATH, as intended
make: *** [verify-python-version] Error 1

Why CI opts out

MISE falls back to $(HOME)/.local/bin/mise whether or not anything is there, so on a machine without mise, MISE_EXEC prefixes every uv call with a binary that does not exist. CI is exactly that machine: the Python jobs install uv through astral-sh/setup-uv and never install mise, which reaches verify-mise only via bootstrap-studio. The first push of this branch failed four jobs on it:

env: '/home/runner/.local/bin/mise': No such file or directory
make: *** [Makefile:387: test-unit-ci] Error 127

test-unit-ci, test-integration-ci (unit / integration / e2e), and update-licenses, vendor, generate-cli-commands, check-copyright-headers (Lint all).

Setting NMP_SKIP_MISE=1 at the workflow level is the fix rather than installing mise in CI, because CI is already pinned from the same source of truth — setup-uv is configured with version-file: pyproject.toml, so it resolves uv from the same required-version constraint that uv = "0.9" was chosen to satisfy, and actions/setup-node pins Node for the web jobs. What mise adds is protection against a global uv outside required-version winning on PATH, which is a developer-machine problem; a fresh runner has no such uv. Installing mise per job would also pull node and pnpm onto Python-only jobs and spend GitHub API requests against the 60/hr unauthenticated ceiling for no pin that isn't already there.

Only ci.yaml needs it. ngc-metadata.yaml and insights-testbed.yml call uv run directly rather than through make, so MISE_EXEC never applies, and publish-fern-docs.yaml's make docs-check is npm-only.

On the GitHub rate limit

pnpm and uv are both fetched through the GitHub API (aqua:pnpm/pnpm, aqua:astral-sh/uv), which allows 60 unauthenticated requests per hour per IP. That is enough to fail a bootstrap behind a shared NAT, and it affects the pnpm install from #1109 as well — earlier runs simply had headroom. Observed on a VM with the limit exhausted:

aqua:astral-sh/uv@0.9: GitHub artifact attestations verification failed:
  403 API rate limit exceeded for <ip>
aqua:pnpm/pnpm@10.34: 403 Forbidden for .../repos/pnpm/pnpm/releases/tags/v10.34.5

Node is unaffected — it comes from nodejs.org.

Download mirrors (url_replacements) don't help here, since the failing calls are metadata and attestation endpoints rather than release-asset downloads. Disabling aqua verification would cut some calls but trades away the integrity check. A token is the cheap fix: gh auth login covers most developers. The token is read inside the recipe shell, so it never enters make's variable space or make -n output.

Test plan

macOS (arm64):

make verify-mise installs uv 0.9.30; mise exec -- uv --version → uv 0.9.30.
make verify-python-version exits 0 and installs Python 3.12.12 through the mise-managed uv.
uv lock --check against the real workspace resolves 582 packages, lockfile in sync.
make -n test-unit-ci expands to "…/mise" exec -- uv run --frozen pytest …; with NMP_SKIP_MISE=1 it expands to bare uv run. Same for the other five targets that failed CI.
With the IP at 0/60 unauthenticated and no token in the environment, the gh fallback completes the install; make -n verify-mise shows the gh auth token call but never the token.

Ubuntu 26.04 (aarch64) VM, no node/pnpm/uv/mise installed:

Unauthenticated install with the limit exhausted fails with the new diagnostic rather than a raw 403 trace.
Full authenticated install of node + pnpm + uv on the VM — pending; not run because it would have required sending a GitHub token to that host.

CI:

Green run on this branch: Lint all, Python unit, integration and e2e tests all pass on fdf38e5.

Known limitation: `make` targets assume bootstrap ran

Only the bootstrap chain installs mise (verify-mise). On main all four MISE_EXEC users reach it; this branch adds 34 that don't — the test-* targets, update-licenses, vendor, refresh-openapi, generate-cli-*, check-licenses, docs-*, bootstrap-plugins, run, benchmark-guardrails. On a machine without mise they fail with Error 127 instead of falling back:

$ make test-markers MISE=/nonexistent/mise
"/nonexistent/mise" exec -- uv run --frozen pytest --markers
/bin/sh: /nonexistent/mise: No such file or directory
make: *** [test-markers] Error 127

make bootstrap is the documented first step, so the normal path is unaffected — this bites someone who already has uv and jumps straight to make test-unit. Documented in SETUP.md with the symptom and the fix rather than adding a verify-mise prerequisite to all 34, which would run mise install --yes on every make test-*.

Known gap: pre-commit still uses the global uv

Five hooks in .pre-commit-config.yaml are language: system and resolve uv off PATH — uv-lock, copyright-fix, config-reference-docs, and the ty / openapi-generator hooks via the scripts they call. A global uv outside required-version still blocks any commit touching pyproject.toml. Pre-existing rather than a regression here, and fixing it properly means a shared script/uv shim that both the Makefile and pre-commit resolve through, which is a bigger change than this branch should carry. Tracked in #1161.

Notes

#1109 has merged, so this branch was rebased onto main and now targets main directly.

The GITHUB_TOKEN fallback and the rate-limit diagnostic also cover the pnpm install added in #1109.

Summary by CodeRabbit

Chores
- Updated project tooling to use Python 3.12 and uv 0.9.
- Standardized development, documentation, testing, and runtime commands.
- Improved setup and verification, including authentication and rate-limit guidance.
- CI now consistently uses workflow-provisioned toolchains.
Documentation
- Clarified setup instructions for pinned uv, Node.js, and pnpm versions.
- Added guidance for bootstrapping, direct uv usage, and using an existing local toolchain.

marcusds · 2026-08-06T19:20:48Z

Before on a fresh checkout on a system with an out of range version of UV:

$ make bootstrap
local system architecture: linux/amd64
~~~~~~
installing python dependencies
uv sync --frozen --all-packages
error: Required uv version `>=0.9.14, <0.10.0` does not match the running version `0.11.4`
make: *** [Makefile:190: bootstrap-python] Error 2

After:

$ make bootstrap
local system architecture: linux/amd64
mise: installing mise...
######################################################################## 100.0%
mise: installed successfully to /home/marcus/.local/bin/mise
mise: run the following to activate mise in your shell:
echo "eval \"\$(/home/marcus/.local/bin/mise activate bash)\"" >> ~/.bashrc

mise: run `mise doctor` to verify this is set up correctly
gpg: Signature made Wed 29 Jul 2026 06:56:01 AM PDT
gpg:                using RSA key CC68F5A3106FF448322E48ED27F5E38D5B0A215F
gpg: Good signature from "marco-ippolito <[marcoippolito54@gmail.com](mailto:marcoippolito54@gmail.com)>" [unknown]
gpg: Signature notation: manu=2,2.5+1.12,0,3
mise 2026.5.7 by @jdx                                                                                          [3/3]
uv@0.9.30       extract uv-x86_64[-unknown-linux-musl.tar.gz](about:blank)                                                        ✔
node@22.23.2    10.9.8                                                                                             ✔
pnpm@10.34.5    extract pnpm-linux-x64                                                                             ✔
~~~~~~
installing python dependencies
"/home/marcus/.local/bin/mise" exec -- uv sync --frozen --all-packages
Using CPython 3.12.13
Creating virtual environment at: .venv
...

After this nemo services run was successful

Bootstrap assumed a uv on PATH inside pyproject.toml's `required-version = ">=0.9.14,<0.10.0"`, with README and AGENTS.md telling people to install a matching one by hand. Pin uv in mise.toml alongside node and pnpm, add `UV := $(MISE_EXEC) uv`, and route every uv invocation in the Makefile through it so `make test-unit`, `make bootstrap-python` and friends use the pinned version regardless of what is on PATH. NMP_SKIP_MISE=1 still falls back to bare `uv`. Default PYTHON_VERSION to 3.12. It was 3.11, which no longer satisfies `requires-python = ">=3.12,<3.15"`, so `uv python install` fetched an interpreter the project cannot use while `uv venv` quietly picked a different one. pnpm and uv are both fetched through the GitHub API, which allows 60 unauthenticated requests per hour per IP — enough to fail a bootstrap on a shared NAT or a CI runner. Reuse a GITHUB_TOKEN from the environment or the gh CLI when one is available, and explain the rate limit when the install fails instead of surfacing a bare 403. Signed-off-by: mschwab <mschwab@nvidia.com>

github-actions · 2026-08-07T00:25:15Z

Suite	Lines Covered	Line Rate	Branch Rate
Unit Tests	31439/40061	78.5%	63.0%
Integration Tests	18308/38013	48.2%	20.8%

Routing every uv call through `mise exec --` broke CI: the Python jobs install uv with astral-sh/setup-uv and never install mise, so `make test-unit-ci`, `test-integration-ci`, `update-licenses`, `vendor`, `generate-cli-commands` and `check-copyright-headers` all died with env: '/home/runner/.local/bin/mise': No such file or directory make: *** [Makefile:387: test-unit-ci] Error 127 MISE falls back to $(HOME)/.local/bin/mise whether or not anything is there, so MISE_EXEC prefixed a binary that does not exist. Set NMP_SKIP_MISE=1 for the workflow. setup-uv already resolves uv from pyproject.toml's required-version — the same constraint mise.toml's `uv = "0.9"` was chosen to satisfy — and actions/setup-node pins Node for the web jobs, so nothing here needs the mise-managed toolchain. The pin mise adds is for developer machines, where a global uv outside required-version can win on PATH; CI has no such uv. Only ci.yaml needs this. ngc-metadata.yaml and insights-testbed.yml call `uv run` directly rather than through make, so MISE_EXEC never applies, and publish-fern-docs.yaml's `make docs-check` is npm-only. Signed-off-by: mschwab <mschwab@nvidia.com>

ironcommit

LGTM

Routing uv through `mise exec --` means targets that call uv now depend on mise being installed, and only the bootstrap chain installs it. Run `make test-unit` on a fresh clone and you get /bin/sh: /Users/you/.local/bin/mise: No such file or directory make: *** [test-unit] Error 127 which says nothing about what to do. Document the ordering in SETUP.md with the symptom, the fix, and the NMP_SKIP_MISE=1 opt-out. Also drop the advice this branch obsoletes. AGENTS.md told Cursor Cloud users to `pip install 'uv>=0.9.14,<0.10.0'` before bootstrapping and README.md listed a matching uv as a prerequisite for the source checkout; mise now supplies it, and a global uv outside the range no longer has to be downgraded. Signed-off-by: mschwab <mschwab@nvidia.com>

coderabbitai · 2026-08-07T01:37:25Z

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

@coderabbitai resume to resume automatic reviews.
@coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

▶️ Resume reviews
🔍 Trigger review

📝 Walkthrough

Walkthrough

The PR pins uv 0.9, routes Makefile Python commands through mise, updates Python to 3.12, improves mise authentication handling, and configures CI and documentation for the shared toolchain.

Changes

Python toolchain execution

Layer / File(s)	Summary
Toolchain configuration and verification `mise.toml`, `Makefile`	The project pins uv 0.9. The Makefile defines a shared uv command and adds GitHub authentication and mise failure reporting.
Python version and bootstrap flow `Makefile`	The default Python version is 3.12. Python verification, virtual-environment creation, and dependency synchronization use the shared uv command.
Makefile command migration `Makefile`	Generation, documentation, licensing, vendor, runtime, test, benchmark, Docker, Kubernetes, and GPU targets use the shared uv command.
CI and setup integration `.github/workflows/ci.yaml`, `AGENTS.md`, `README.md`, `SETUP.md`	CI skips mise when workflow steps provide the toolchains. Project guidance describes mise-managed uv, Node.js, and pnpm workflows.

Sequence Diagram(s)

sequenceDiagram
  participant Makefile
  participant GitHubCLI
  participant mise
  participant uv
  Makefile->>GitHubCLI: request gh auth token when GITHUB_TOKEN is unset
  GitHubCLI-->>Makefile: return GitHub token
  Makefile->>mise: install pinned tools
  mise-->>Makefile: provide configured toolchain
  Makefile->>uv: run Python commands through MISE_EXEC

Possibly related PRs

NVIDIA-NeMo/nemo-platform#1109: Updates the Makefile and documentation for pinned tools managed through mise, including NMP_SKIP_MISE=1 and verify-mise.
NVIDIA-NeMo/nemo-platform#1146: Updates uv toolchain and version management across CI and development setup.

Suggested labels: chore

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: managing uv through mise during bootstrap.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests
Commit unit tests in branch mise-manage-uv/mschwab

_{Comment @coderabbitai help to get the list of available commands.}

coderabbitai

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Makefile`:
- Line 20: Update the Makefile commands invoking uv venv and uv sync to pass
--python $(PYTHON_VERSION), ensuring the configured interpreter controls
environment creation and synchronization. Also add verify-python-version as a
prerequisite of the bootstrap-python target.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: e5f734d8-9a32-40b0-801a-6c4faa32c019

📥 Commits

Reviewing files that changed from the base of the PR and between 0d95ddb and fdf38e5.

📒 Files selected for processing (3)

.github/workflows/ci.yaml
Makefile
mise.toml

coderabbitai

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Around line 42-43: Update the README prerequisites wording around the make
bootstrap guidance to distinguish required source-development tools, especially
Git and GNU Make, from the pinned uv, Node.js, and pnpm versions installed by
bootstrap. Do not state that the preceding prerequisites apply only to PyPI
installation; clarify that bootstrap installs tool versions but still requires
Git and GNU Make.

In `@SETUP.md`:
- Around line 104-107: Update the fenced code block in SETUP.md containing the
`/bin/sh` and `make: *** [test-unit] Error 127` output to specify the `text`
language tag, preserving the displayed command output unchanged.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 97fc8649-f3d2-4f27-b9e4-db9e4b7a8b90

📥 Commits

Reviewing files that changed from the base of the PR and between fdf38e5 and 52270f7.

📒 Files selected for processing (3)

AGENTS.md
README.md
SETUP.md

`uv venv` and `uv sync` were choosing an interpreter on their own. `requires-python = ">=3.12,<3.15"` accepts 3.12, 3.13 and 3.14, so `verify-python-version` would find or install PYTHON_VERSION and then `uv venv` built the environment against something else entirely: $ uv python find 3.12 $ uv venv --seed --allow-existing $ .venv/bin/python --version Python 3.13.3 Pass `--python $(PYTHON_VERSION)` to both, which pins it (3.12.12 in the same check), and make `bootstrap-python` depend on `verify-python-version` so the interpreter exists before the sync rather than only when someone runs the verify target directly. Only the guardrails benchmark job runs `make bootstrap-python`, and it already pins python-version 3.12; the 3.12/3.13 wheel matrices build without it, so nothing in CI changes interpreter. Also correct the README claim that the listed prerequisites apply only to the PyPI install — Git and GNU Make are still needed from source — and give the Error 127 block in SETUP.md a language tag (MD040). Signed-off-by: mschwab <mschwab@nvidia.com>

coderabbitai

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

Makefile (1)
168-179: 🩺 Stability & Availability | 🟠 Major | ⚡ Quick win

Add the mise prerequisite to .venv/bin/python.

This target has no prerequisite, but its recipe invokes $(UV). Unless NMP_SKIP_MISE=1, this expands to mise exec -- uv. A direct make .venv/bin/python can therefore run before verify-mise installs mise.

Add verify-python-version or verify-mise as a prerequisite.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@Makefile` around lines 168 - 179, Add verify-python-version or verify-mise as
a prerequisite to the .venv/bin/python target so direct invocations validate the
required mise/UV setup before executing the recipe. Preserve the existing
virtual-environment creation logic and BOOTSTRAP_CREATE_VENV guard.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Makefile`:
- Line 178: Update the venv setup recipe around the existing “uv venv” command
to detect whether .venv/bin/python reports a different version than
PYTHON_VERSION. When the versions differ, remove or clear the existing
environment and recreate it with uv venv --clear; otherwise preserve the current
environment setup behavior.

---

Outside diff comments:
In `@Makefile`:
- Around line 168-179: Add verify-python-version or verify-mise as a
prerequisite to the .venv/bin/python target so direct invocations validate the
required mise/UV setup before executing the recipe. Preserve the existing
virtual-environment creation logic and BOOTSTRAP_CREATE_VENV guard.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

Push a commit to this branch (recommended)
Create a new PR with the fixes

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: e52683c6-e1b7-43ec-90c5-e30ec86dc7ed

📥 Commits

Reviewing files that changed from the base of the PR and between 52270f7 and 58f25e3.

📒 Files selected for processing (3)

Makefile
README.md
SETUP.md

🚧 Files skipped from review as they are similar to previous changes (2)

README.md
SETUP.md

The target had no prerequisites but its recipe calls $(UV), which expands to `mise exec -- uv` unless NMP_SKIP_MISE is set. A direct `make .venv` — or `make bootstrap-plugins`, which depends on it — could therefore run before anything installed mise. Make `verify-python-version` an order-only prerequisite. A normal one would force the recipe on every invocation, since a phony prerequisite is always newer than the target file, and re-seed an existing venv each time; order-only runs the check but leaves an up-to-date venv alone. That also makes the `uv python find || uv python install` line inside the recipe redundant with the one in verify-python-version, so drop it. Signed-off-by: mschwab <mschwab@nvidia.com>

`.venv/bin/python` existing says nothing about which interpreter built it, so as a file target make skipped the recipe and a stale venv survived a PYTHON_VERSION change: $ .venv/bin/python -V # PYTHON_VERSION = 3.12 Python 3.13.3 $ make .venv make: Nothing to be done for `.venv'. Make it phony and compare the interpreter instead. On a match the recipe exits early, so an up-to-date venv is never rebuilt; on a mismatch it recreates with `--clear` and says what changed. `--clear` matters because `--allow-existing` leaves the old tree behind — a 3.13 venv rebuilt at 3.12 keeps `lib/python3.13` next to `lib/python3.12`. `bootstrap-python` already self-healed through `uv sync --python`; this covers `make .venv` and `make bootstrap-plugins` reached on their own. Signed-off-by: mschwab <mschwab@nvidia.com>

Wrapper targets escaped mise. `stainless`, `lint`, `lint-fix` and `vendor-nemo-platform-ext` hand off to a script or a sub-make that calls bare `uv` — 9 of the 13 scripts behind `lint-all.sh` do, as do `sdk/stainless.sh` and `packages/nemo_platform_ext/Makefile`. So `make update-sdk`, `make update-cli`, `make lint` and `make lint-fix` still broke against a global uv outside `required-version`, which is the case this branch exists to fix. Route the four through $(MISE_EXEC); scripts already invoked via $(UV) are fine, since `mise exec` puts the pinned uv on PATH for the whole subprocess tree. Patch-level PYTHON_VERSION never matched. The probe reported major.minor and compared it literally, so PYTHON_VERSION=3.13.3 against a 3.13.3 venv read as "3.13 != 3.13.3" and cleared the environment on every invocation — including, with BOOTSTRAP_LOCAL_PLUGIN_DIRS set, the freshly synced one immediately before installing local plugins. Compare the full version and treat PYTHON_VERSION as a selector, so 3.13 matches any 3.13.x and 3.13.3 matches exactly. A damaged .venv could not be repaired. `--clear` was gated on the interpreter probe succeeding, so a .venv whose python was missing or non-executable ran `uv venv` with neither --clear nor --allow-existing and failed with "A directory already exists". Gate it on the directory instead. Signed-off-by: mschwab <mschwab@nvidia.com>

github-actions Bot added the build conventional-commit type label Aug 6, 2026

Base automatically changed from astd-148-mise-nodejs-pnpm-bootstrap/mschwab to main August 7, 2026 00:14

marcusds force-pushed the mise-manage-uv/mschwab branch from caedda3 to aa33a34 Compare August 7, 2026 00:21

marcusds marked this pull request as ready for review August 7, 2026 01:32

marcusds requested review from a team as code owners August 7, 2026 01:32

ironcommit approved these changes Aug 7, 2026

View reviewed changes

coderabbitai Bot reviewed Aug 7, 2026

View reviewed changes

Comment thread Makefile

coderabbitai Bot reviewed Aug 7, 2026

View reviewed changes

Comment thread README.md Outdated

Comment thread SETUP.md Outdated

coderabbitai Bot reviewed Aug 7, 2026

View reviewed changes

Comment thread Makefile Outdated

marcusds added 3 commits August 6, 2026 21:29

marcusds mentioned this pull request Aug 7, 2026

Pre-commit hooks bypass the mise-pinned uv #1161

Open

svvarom self-requested a review August 7, 2026 16:37

svvarom approved these changes Aug 7, 2026

View reviewed changes

marcusds added this pull request to the merge queue Aug 7, 2026

Merged via the queue into main with commit ff047d2 Aug 7, 2026
97 of 98 checks passed

marcusds deleted the mise-manage-uv/mschwab branch August 7, 2026 17:01

coderabbitai Bot mentioned this pull request Aug 7, 2026

build: allow newer uv for source checkouts #1146

Merged

8 tasks

Navigation Menu

Uh oh!

build(bootstrap): manage uv with mise - #1134

build(bootstrap): manage uv with mise#1134
marcusds merged 7 commits into
mainfrom
mise-manage-uv/mschwab

marcusds commented Aug 6, 2026 •

edited

Loading

Uh oh!

marcusds commented Aug 6, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 7, 2026 •

edited

Loading

Uh oh!

ironcommit left a comment

Uh oh!

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading

Reviews paused

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

marcusds commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Global uv version mismatches

Why CI opts out

On the GitHub rate limit

Test plan

Known limitation: make targets assume bootstrap ran

Known gap: pre-commit still uses the global uv

Notes

Summary by CodeRabbit

Uh oh!

marcusds commented Aug 6, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ironcommit left a comment

Choose a reason for hiding this comment

Uh oh!

coderabbitai Bot commented Aug 7, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviews paused

Walkthrough

Changes

Sequence Diagram(s)

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

coderabbitai Bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

marcusds commented Aug 6, 2026 •

edited

Loading

Known limitation: `make` targets assume bootstrap ran

marcusds commented Aug 6, 2026 •

edited

Loading

github-actions Bot commented Aug 7, 2026 •

edited

Loading

coderabbitai Bot commented Aug 7, 2026 •

edited

Loading