modules.vlang.io stale since 4 October 2026; recent module docs CI runs fail at Build V

Summary

As of 18 October 2026, https://modules.vlang.io/ and https://modules.vlang.io/builtin.html still show:

Powered by vdoc. Generated on: 4 Oct 2026 05:47:21

Recent completed master/push runs of the vlib modules CI workflow fail at Build V, so documentation generation and production deployment are skipped.

This appears to be a new publishing interruption after #29173 was resolved. This report does not assume the previous vdoc crash has returned.

Reproduction

1. Open either URL above and inspect its footer.
2. The timestamp is also present in the HTML returned by direct HTTP requests, not only in a browser-rendered page. Adding a query parameter and requesting Cache-Control: no-cache still returned the same timestamp during this check.

The footer is generated from d.time_generated (time.now()) by cmd/tools/vdoc/utils.v: it is embedded during generation, not updated on each visit.

CI evidence

These recent completed master/push runs all fail at Build V (make -j4 && ./v symlink):

• https://github.com/vlang/v/actions/runs/39035310369/job/117421055489 — job started 18 October 2026, 06:15 UTC.
• https://github.com/vlang/v/actions/runs/39001663509/job/117360709741 — job started 17 October 2026, 14:31 UTC.
• https://github.com/vlang/v/actions/runs/38942492395/job/117199313850 — job started 17 October 2026, 09:13 UTC.

In each run, Test v doc, Build module documentation and check the examples in the comments, and Deploy docs to vercel are skipped. The checks annotations report exit code 2. Workflow: .github/workflows/module_docs_ci.yml.

I could verify step conclusions through the public API, but could not retrieve full build logs through the unauthenticated logs endpoint. The exact failing bootstrap/compiler command is therefore not established here. This report does not attribute the failure to Vercel caching, deployment credentials, or the previously fixed vdoc bug.

Expected behavior

Please investigate the Build V failure, restore successful documentation generation and production deployment, and verify that the live site reflects a recent source revision.

HTTP Last-Modified values differed from the embedded generation date during the check; those headers alone do not demonstrate fresh documentation generation. These observations also do not identify the deployment that originally published the 4 October files.

Related, previously resolved report: #29173.