☂️ Release remote caching
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 5/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- github-actions, rust
- 领域
- build-system, cloud
调研方向
This is a tracking issue for the remote cache release, not a single change. Start with the roadmap items #929 and #931, which hold the actual work, and the open items under Later. Done means #768 and #781 are fixed, remote caching is documented, and the Cloudflare server repository has been released alongside the client.
由索引模型根据 Issue 内容生成。
描述
Part of the 2026 Q4 plan (P0).
Goal
Test remote caching in real projects and release it, together with Vite+'s Cloudflare Workers implementation in voidzero-dev/vite-plus-remote-cache-cloudflare.
Roadmap
- Cache tools that maintain their own cache: #929. In trials on real workspaces, most tasks either couldn't be cached or missed on every fresh checkout, so a remote cache would have had little to share.
- Reuse entries across main and pull requests, safely: #931.
- Ship: fix #768 and #781, and document remote caching.
Done
- Configuration, upload and restore: #725, #726, #727, #740, #744, #754, #755, #756, #757
- Hardening: #764, #770, #771, #772, #786
- Background uploads and HTTP/2: #787, #795
- Uploads authenticated with GitHub Actions OIDC: #691, #797, #798
- Windows e2e: #841, #844
- Server: moved from #718 to its own repository, serving voidzero-dev/void (voidzero-dev/vite-plus-remote-cache-cloudflare#13 and voidzero-dev/vite-plus-remote-cache-cloudflare#17)
Later
- #924 A remote hit is never stored back
- #926 Keys always include the OS and architecture
- #888 Output archives larger than the server's request limit
- #717, #790 Entries that embed machine-specific paths (#789)
- #906 OpenTelemetry client spans (#907)
All pull requests: label:"remote cache"
- 主要语言
- Rust
- 星标
- 485
- 派生
- 51
- 平均合并
- 23 小时 40 分钟
- 30 天内合并 PR
- 55
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
voidzero-dev/vite-task 的其他 Issue
-
fspy linux backend
难度 5/5 一周以上 新手友好度 6/100
voidzero-dev/vite-task#932 ·
维护者通常 1 天内回复
-
remote cache
难度 5/5 一周以上 新手友好度 12/100
voidzero-dev/vite-task#931 ·
维护者通常 1 天内回复
-
read-write overlap
难度 5/5 一周以上 新手友好度 5/100
voidzero-dev/vite-task#929 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 50/100
voidzero-dev/vite-task#928 ·
维护者通常 1 天内回复
-
remote cache
难度 4/5 3-5 天 新手友好度 32/100
voidzero-dev/vite-task#926 ·
维护者通常 1 天内回复
查看 voidzero-dev/vite-task 的全部 Issue
相似的 Issue
-
bug file-compat priority: high
难度 2/5 1-3 小时 新手友好度 76/100
storytold/photocraft#11330 · 1 条评论 ·
维护者通常 1 天内回复
-
redis-compat
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
say: name hint should only fire on @tags, not bare words or text inside links可能已有人在做 @morganparadis 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
CakeRepository/agentshangout#501 ·
-
area:ui could docs good first issue
难度 1/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100