go.work workspace setup with CI pollutes Go module cache

[bgentry]

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.

[brandur]

Including [skip ci] in your commit/PR description and that'll do the trick, and also avoid all the concerning looking Xes on the CI job statuses in the PR. Not the greatest thing in the world, but we can get this scripted at some point so it's harder to forget.