go.work workspace setup with CI pollutes Go module cache
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 179
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 13
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100