feat(remote-cache): add self-hosted public cache server

[fengmk2]

Add packages/remote-cache for the server in #716, using Cloudflare Workers, primary D1 metadata, and a private R2 bucket. The server supports public reads and GitHub Actions OpenID Connect checks for writes. Stores use streaming uploads, atomic publication, storage limits, and automatic data expiry.

One workflow deploys related changes to a persistent staging Worker, D1 database, and R2 bucket. Internal PRs, main pushes, and manual runs share these resources. The workflow runs deployments and smoke tests in sequence, then updates PR comments with the tested revision and manual instructions. Each deployment replaces the previous revision. Closing a PR keeps staging available. Setup uses repository secrets and variables. Repository maintainers can configure staging without a GitHub environment.

The e2e plan defines automated checks and manual exercises. PR runs check public reads and rejected writes. Pushes to main also check authorized uploads, multipart storage, replacement, concurrency, and quotas. Local tests repeat smoke checks against reused storage and retain maximum-payload and scheduled-handler coverage. Real Cron execution and maximum payloads on Cloudflare require separate release exercises.

/fetch returns only { kind: "fallback", key } for fallback matches and does not read R2. Exact matches return the value and blob_id. A missing or unreadable exact value returns 503. Fetch misses and unavailable blobs return plain-text 404, as specified in the local RFC.

Setup rejects incompatible origins and repositories before it changes existing policies or saved configuration. Each Worker has separate rate-limit counters that remain stable across revisions. Workers Free CPU support remains unverified. The guide recommends Workers Paid for the full payload limits.

Motivation

Maintainers need a cache service in their own Cloudflare account. Developers and fork contributors must reuse public task results without login. Only trusted jobs on main should publish those results. Reviewers need one persistent staging environment and a clear verification result after each related change.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​esbuild@​0.28.1
	npm/​tsx@​4.23.13
	npm/​jsonc-parser@​3.3.1
	npm/​wrangler@​4.131.1
	npm/​jose@​6.2.12
	npm/​cborg@​6.1.2
	npm/​@​cloudflare/​workers-types@​5.20260911.1
	npm/​miniflare@​5.20260911.0-alpha

View full report

[github-actions]

fspy benchmark

linux

dynamic/launch             change  +0.91%  [ -5.81% ..  +7.55%]  overhead  +292.32%
dynamic/access             change  +0.30%  [ -1.63% ..  +4.63%]  overhead   +14.48%
dynamic/access-relative    change  +0.11%  [ -1.93% ..  +1.36%]  overhead   +59.28%
dynamic/access-contended   change  +0.40%  [-13.48% ..  +4.43%]  overhead   +14.43%
static/launch              change  -0.10%  [ -5.41% ..  +6.32%]  overhead  +747.10%
static/access              change  -0.00%  [ -1.95% ..  +1.59%]  overhead  +810.79%
static/access-relative     change  -0.11%  [ -1.45% ..  +1.67%]  overhead +1378.82%
static/access-contended    change  -0.05%  [ -8.10% ..  +2.48%]  overhead +3118.95%

macos

dynamic/launch             change  +0.37%  [ -4.01% ..  +5.00%]  overhead  +240.74%
dynamic/access             change  +0.32%  [-20.80% ..  +8.61%]  overhead    +7.70%
dynamic/access-relative    change  -1.27%  [-26.94% ..  +9.86%]  overhead  +260.87%
dynamic/access-contended   change  +1.74%  [ -7.51% .. +34.70%]  overhead    +4.77%

windows

dynamic/launch             change  -0.99%  [-11.36% ..  +8.94%]  overhead   +27.05%
dynamic/access             change  +1.20%  [-13.58% .. +27.46%]  overhead    +2.26%
dynamic/access-relative    change  -0.33%  [ -9.46% ..  +3.70%]  overhead    +1.38%
dynamic/access-contended   change  +0.43%  [-10.65% ..  +7.96%]  overhead    +3.51%

[github-actions]

Remote cache staging

Commit: 0c55376f703fa7456db036ea15996bdf4834c523

Cloudflare deployment or e2e verification failed. The staging deployment is not marked ready. See the workflow run.

Manual checks and complete e2e plan.

[fengmk2]

Deploy prompt:

Refer to the deployment instructions at https://github.com/voidzero-dev/vite-task/blob/feat/public-remote-cache/packages/remote-cache/docs/self-hosting.md to deploy a remote cache service for the current repo.