Skip to content

docs: disable uv cache in the docs build - #30

Merged
coretl merged 1 commit into
mainfrom
docs-uv-disable-cache
Jun 26, 2026
Merged

coretl merged 1 commit into
mainfrom
docs-uv-disable-cache

Conversation

@coretl

@coretl coretl commented Jun 26, 2026 •

Copy link
Copy Markdown
Contributor

The docs build installs uv only to put it on PATH — build-command owns dependency install — so there are no requirements/pyproject/uv.lock files to key the cache on, and setup-uv warned "cache will never get invalidated" every run.

Set enable-cache: false. uv's own download is small, so skipping it is cheap. (A uv-heavy consumer of the reusable docs.yml loses the uv download cache, but build time is dominated by myst/npm; if one ever needs it, the clean follow-up is a docs.yml input to toggle it.)

setup-uv stays pinned to the full v8.2.0 — it ships immutable releases, so there's no floating @v8 major tag to track (Renovate manages the bumps).

🤖 Generated with Claude Code

The docs build installs uv only to put it on PATH; build-command owns dependency
install. With no requirements/pyproject/uv.lock to key on, setup-uv's default
cache emitted a "cache will never get invalidated" warning every run. Set
enable-cache: false. (setup-uv stays pinned to the full v8.2.0 — it uses immutable
releases, so there's no floating @v8 major tag to track.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coretl
coretl force-pushed the docs-uv-disable-cache branch from 3e59384 to cb0eef3 Compare June 26, 2026 10:20
@coretl coretl changed the title docs: disable uv cache + float setup-uv to @v8 docs: disable uv cache in the docs build Jun 26, 2026
@coretl
coretl merged commit df88304 into main Jun 26, 2026
7 checks passed

This branch was previously deployed

1 inactive deployment
github-pages — cb0eef38 Deployed Jun 26, 2026 by coretl via publish / deploy / publish #96
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant