Visitar URL original
ci(docs): cache the docs tasks with vp run and a remote cache by wan9chi · Pull Request #11653 · rolldown/rolldown · GitHub
Skip to content

ci(docs): cache the docs tasks with vp run and a remote cache - #11653

Draft
wan9chi wants to merge 1 commit into
rolldown:mainfrom
wan9chi:ci/docs-remote-cache
Draft

wan9chi wants to merge 1 commit into
rolldown:mainfrom
wan9chi:ci/docs-remote-cache

Conversation

@wan9chi

@wan9chi wan9chi commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Why

Docs Validation regenerates the API reference and rebuilds the docs on every PR push, even when nothing they depend on changed. This caches both tasks with vp run and its remote task cache, so PRs reuse what main has built.

Changes

  • The docs tasks are cached. docs/vite.config.ts defines generate and build as vp run tasks. vp run tracks the files each one reads, so they need no input config.
  • void deploy is split into build and deploy. void deploy built the site itself, so its build couldn't be cached. Deploy to Void now builds with vp run docs:build, then deploys the result with void deploy --dir .vitepress/dist.

Numbers

From replaying this workflow's runs from Oct 24 to Nov 9

  • Same-repo PR jobs: 55 s median, down from 80 s.
  • Cache hits on those PRs: 74% for generate, 67% for build.
  • False hits: 0.

@socket-security

socket-security Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​@​voidzero-dev/​vite-task-client@​0.2.0721009393100

View full report

Define the docs `generate` and `build` tasks in docs/vite.config.ts so `vp run` caches them, and run
them through `vp run` from the root `docs:build` script. Deploy to Void now builds with `vp run`
before `void connect` and `void deploy`, which deploys the built folder, and uploads the results on
pushes to main. Docs Validation reads them. `void connect` writes docs/.void, which the docs build
lists, so the build runs first to match the PR builds. The root `docs:void` script, which only
Deploy to Void ran, is removed.

The docs config reads the Algolia keys through `getEnv`, which makes them part of the build's cache
key. Docs Validation's build gets the same keys, so its builds match the deploy's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wan9chi
wan9chi force-pushed the ci/docs-remote-cache branch from 4540db1 to 9e08de9 Compare November 11, 2026 11:17

@fengmk2 fengmk2 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.
@shulaoda can you take a look?

This branch has not been deployed

No deployments
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.

2 participants