go.mod/go.sum cleanup, docsy → v0.6.0, pin Netlify Hugo#5021
Open
go.mod/go.sum cleanup, docsy → v0.6.0, pin Netlify Hugo#5021
Conversation
✅ Deploy Preview for viam-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
The recorded hashes for docsy v0.2.0 and v0.5.0 in go.sum did not match the canonical hashes published by sum.golang.org, causing checksum verification failures. Regenerated go.sum with verified hashes for the versions actually resolved by the module graph. Also cleaned up go.mod: dropped the stale v0.2.0 require (MVS already resolved to v0.5.0 transitively), removed `// indirect` markers since both modules are direct Hugo imports per config.toml, and bumped the go directive from 1.12 to 1.23. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
docsy v0.5.0's go.mod requires `dependencies@v0.5.0-0.<timestamp>-<hash>`, a malformed pseudo-version (`-0.` prefix on the same base version implies a negative patch number). Modern Go toolchains reject it, so `go mod verify` fails on the resolved graph. v0.6.0 uses a properly-tagged `dependencies@v0.6.0` require, so verification passes. Also pulls Bootstrap from v4.6.1 to v4.6.2 (stays on 4.x — Bootstrap 5 arrives in docsy v0.7.0) and bumps Font-Awesome. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Netlify's default Hugo image had drifted past the version that tolerates docsy's `list.rss.xml` referencing `.Site.Author.email` — a deprecated field that newer Hugo treats as a hard error. GitHub Actions builds already pin `hugo-version: 0.152.2` (the version recorded as successfully tested in `config.toml`'s module.hugoVersion.min); pin Netlify to the same value so previews and the production deploy use the same Hugo as CI. This will be revisited when Hugo is bumped in phase 2 of the dependency cleanup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fdb7c35 to
62bd8a5
Compare
ale7714
approved these changes
Apr 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
The
go.sumfile contained incorrect hashes forgithub.com/google/docsy(bothv0.2.0andv0.5.0) that did not match the canonical hashes published bysum.golang.org, causing checksum verification failures ongo mod download. This PR regeneratesgo.sumwith verified hashes, tidiesgo.mod, bumps docsy fromv0.5.0tov0.6.0sogo mod verifypasses, and pins Netlify's Hugo version to match CI so deploys reproduce the build environment that GitHub Actions already validates against.This is phase 1 of a planned three-phase dependency cleanup. Phase 2 (Hugo bump) and phase 3 (larger docsy upgrade toward
v0.14.x) will follow in separate PRs.Why bump docsy to v0.6.0?
docsy v0.5.0'sgo.modrequiresdependencies@v0.5.0-0.20220905171817-ae8b8117ed16— a malformed pseudo-version (a-0.prefix on the same base version implies a negative patch number). Modern Go toolchains reject it, sogo mod verifyfails on the resolved module graph.v0.6.0uses a properly-taggeddependencies@v0.6.0require, which restores verification.v0.6.0is the smallest possible step that fixes this — Bootstrap stays on 4.x (v5 first arrives indocsy v0.7.0), and the theme templates we render with are unchanged.Why pin HUGO_VERSION on Netlify?
netlify.tomldid not pin a Hugo version, so Netlify used whatever default its build image shipped with. Recent Netlify builds drifted onto a Hugo version that errors hard on.Site.Author.emailaccess (a long-deprecated field still referenced by docsy'slist.rss.xml). GitHub Actions already pinshugo-version: "0.152.2"(the version recorded as "successfully tested" inconfig.toml'smodule.hugoVersion.min), so this commit pins Netlify to the same value. Eliminates drift between CI and Netlify and unblocks the deploy preview. Will be revisited when Hugo itself is bumped in phase 2.Changes
docsy v0.2.0anddocsy v0.5.0did not matchsum.golang.org); regenerated for the newv0.6.0graph. Now contains fullh1:+/go.modhashes for all four modules (docsy,docsy/dependencies,Font-Awesome,bootstrap), each cross-verified againstsum.golang.org.docsyanddocsy/dependenciesfromv0.5.0→v0.6.0. Removed staledocsy v0.2.0require, dropped// indirectmarkers (both modules are direct Hugo imports perconfig.toml), and bumped thegodirective from1.12→1.23.[build.environment] HUGO_VERSION = "0.152.2"to match CI's pinned Hugo version.v4.6.1→v4.6.2; Font-Awesome pin advanced to a 2022-08 commit.Testing
go mod verify→all modules verified✓go mod download -jsonconfirmsSum/GoModSummatch for all four modules in the graph.https://sum.golang.org/lookup/....hugo mod tidyis a no-op against the newgo.mod/go.sum(the module graph is canonical)..Site.Author.emailerror that the Netlify pin works around — confirming the pin is the right fix for the deploy failure rather than a docsy regression.Tickets
None.
Claude Code Prompts Used
go mod verifypassing?"🤖 Generated with Claude Code