Skip to content

ci: request each Go module version on pkg.go.dev after tagging - #130

Merged
JeanExtreme002 merged 1 commit into
mainfrom
ci/request-pkg-go-dev
Oct 18, 2026
Merged

JeanExtreme002 merged 1 commit into
mainfrom
ci/request-pkg-go-dev

Conversation

@JeanExtreme002

@JeanExtreme002 JeanExtreme002 commented Oct 18, 2026 •

Copy link
Copy Markdown
Owner

Why

go/v1.6.3 was tagged, served by proxy.golang.org as @latest and listed in index.golang.org (2026-10-09 19:07 UTC), yet pkg.go.dev never processed it and kept showing v1.6.2 until the version was requested by hand.

What

  • The Tag the Go module step now outputs the version when it pushes the tag, or finds it already pointing at the right commit, so a re-run also repairs a missed version.
  • A new step POSTs to https://pkg.go.dev/fetch/<module>@<version> (what the 404 page's "Request" button does), retrying every 30s up to 10 times while it answers 408.
  • Best effort: it never fails the job, only emits a warning with the link to request manually. Skipped on dry runs.

🤖 Generated with Claude Code

pkg.go.dev never processed go/v1.6.3 even though the proxy and the module
index had it, so the docs stayed on v1.6.2 until it was requested by hand.
The tag job now asks pkg.go.dev for the version it just tagged (or found
already tagged), retrying while it is still processing and only warning
if it never confirms.
@github-actions github-actions Bot added the ci label Oct 18, 2026
@JeanExtreme002
JeanExtreme002 merged commit 88a6bc9 into main Oct 18, 2026
3 of 4 checks passed
@github-actions
github-actions Bot deleted the ci/request-pkg-go-dev branch October 18, 2026 04:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant