fix(hugo): clear deprecation warnings before they break the build (DOCS-150) - #3865
Merged
Conversation
…CS-150) Hugo 0.164.0 emits five deprecation warnings that will become hard errors in a future release. Migrate each to its replacement: - languageCode config key -> locale (v0.158.0) - languages.en.languageName -> label (v0.158.0) - module.mounts.includeFiles -> files (v0.153.0) - .Site.Data -> hugo.Data (v0.156.0) - .Site.LanguageCode -> .Site.Language.Locale (v0.158.0) Verified against Hugo 0.164.0: zero deprecation warnings, build succeeds (1633 pages), and rendered output is unchanged (<html lang=en-US> and the package-mappings tables both intact). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
s-stumbo
approved these changes
Aug 28, 2026
matthewhelmke
deleted the
matthewhelmke/docs-150-resolve-hugo-deprecation-warnings-before-they-break-the
branch
August 28, 2026 15:13
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
2 participants
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.
What
Clears the five Hugo deprecation warnings surfaced by the move to
hugo-extendedunder Dependabot management (see #3858 and the 0.164.0 compat fix #3864). None block the build today, but each becomes a hard error in a future Hugo release — exactly asgetjsonand.Site.Authordid in 0.164.0.Resolves DOCS-150.
Changes
languageCodeconfig keylocaleconfig/_default/config.tomllanguages.en.languageNamelabelconfig/_default/languages.tomlmodule.mounts.includeFilesfilesconfig/_default/config.toml.Site.Datahugo.Datalayouts/partials/notice.html,layouts/shortcodes/package-mappings/{image,fedora,debian}-*.html.Site.LanguageCode.Site.Language.Localelayouts/_default/baseof.htmlA repo-wide grep of
config/andlayouts/confirms these were the only occurrences of all five patterns.Verification
Built with Hugo 0.164.0 (
npm ci && npm run build):deprecated:lines in the output (was 5).<html lang=en-US>renders identically (the newlocalevalue feeds.Site.Language.Locale), and the package-mappings tables still render their data viahugo.Data.0.164.0 is also the latest published
hugo-extendedon npm, so pinned and latest are the same today.Out of scope: the Dart Sass
@import/darken()/slash-div warnings are a separate deprecation track (Bootstrap + our SCSS, not Hugo config).Created in collaboration with Claude Code running Claude Opus 4.8 on 2026-08-28.