go.work workspace setup with CI pollutes Go module cache
还没有人认领这个 Issue。
评估
调研方向
Start by reproducing the release preparation PR and CI behavior on master, focusing on the go.work workspace setup and its effect on the Go module cache. Done means new versions are not cached as unavailable before release and CI succeeds promptly after the release is merged and tags are pushed.
由索引模型根据 Issue 内容生成。
描述
When cutting new releases lately, I've noticed that pushing the "prepare vX.Y.Z" commit & PR for a new version causes the Go module cache the 404 on that new version for a long time (30+ min?) which means that a new version can't actually be used for a long time after it goes out.
Do you think there's anything we can do to avoid polluting the module cache on new versions before they're released @brandur? This also causes CI on master to fail for an extended period of time even after the new release is merged & tags pushed.
Wondering if we might be better off going back to what we had pre-workspaces.
- 主要语言
- Go
- 星标
- 5.7k
- 派生
- 179
- 平均合并
- 2 天 19 小时
- 30 天内合并 PR
- 12
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
riverqueue/river 的其他 Issue
-
难度 5/5 一周以上 新手友好度 45/100
riverqueue/river#1358 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
riverqueue/river#1258 · 7 条评论 ·
-
难度 4/5 3-5 天 新手友好度 45/100
riverqueue/river#1225 · 14 条评论 ·
-
难度 4/5 3-5 天 新手友好度 52/100
riverqueue/river#1185 · 2 条评论 ·
-
难度 4/5 3-5 天 新手友好度 52/100
riverqueue/river#1183 · 2 个 reaction ·
相似的 Issue
-
area/dev-productivity area/disaster-recovery area/ipcei kind/enhancement
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
kind/bug status/0-triage
难度 2/5 1-3 小时 新手友好度 75/100
-
🤔 refinement needed
难度 2/5 1-3 小时 新手友好度 75/100
equinor/radix-operator#1979 ·