cannot run `make serve` at local

[samzong]

This is a Bug Report

x in ~/git/kubernetes/kubernetes-website on main ● ● λ git pull upstream main
From https://github.com/kubernetes/website
 * branch                  main       -> FETCH_HEAD
Already up to date.
x in ~/git/kubernetes/kubernetes-website on main ● ● λ make serve
hugo server --buildDrafts --buildFuture --environment development
Watching for changes in /Users/x/git/kubernetes/kubernetes-website/{archetypes,assets,content,data,i18n,layouts,node_modules,package.json,postcss.config.js,static}
Watching for config changes in /Users/x/git/kubernetes/kubernetes-website/hugo.toml, /Users/x/git/kubernetes/kubernetes-website/node_modules/docsy/config.yaml, /Users/x/git/kubernetes/kubernetes-website/go.mod
Start building sites …
hugo v0.147.9+extended+withdeploy darwin/arm64 BuildDate=2025-06-23T08:22:20Z VendorInfo=brew

Built in 2816 ms
Error: error building site: render: failed to render pages: render of "/Users/x/git/kubernetes/kubernetes-website/content/en/docs/reference/issues-security/official-cve-feed.md" failed: "/Users/x/git/kubernetes/kubernetes-website/layouts/docs/single.html:8:7": execute of template failed: template: docs/single.html:8:7: executing "main" at <partial "docs/content-page" (dict "ctx" . "page" .)>: error calling partial: "/Users/x/git/kubernetes/kubernetes-website/layouts/partials/docs/content-page.html:4:8": execute of template failed: template: _partials/docs/content-page.html:4:8: executing "_partials/docs/content-page.html" at <.page.Content>: error calling Content: "/Users/x/git/kubernetes/kubernetes-website/content/en/docs/reference/issues-security/official-cve-feed.md:39:1": failed to render shortcode "cve-feed": failed to process shortcode: "/Users/x/git/kubernetes/kubernetes-website/layouts/shortcodes/cve-feed.html:5:9": execute of template failed: template: _shortcodes/cve-feed.html:5:9: executing "_shortcodes/cve-feed.html" at <.Err>: can't evaluate field Err in type resource.Resource: Resource.Err was removed in Hugo v0.141.0 and replaced with a new try keyword, see https://gohugo.io/functions/go-template/try/
make: *** [serve] Error 1

Problem: make serve failed.

Proposed Solution:

fix hugo error. Resource.Err was removed in Hugo v0.141.0 and replaced with a new try keyword

Page to Update:
https://kubernetes.io/...

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[samzong]

@lmktfy @tengqm

The root cause of this problem is that my computer uses a newer version of Hugo.

I checked that the latest version of Hugo is 147, while we are currently using version 133. Should we upgrade?

[lmktfy]

/remove-kind bug
/kind support

What benefits do we get from upgrading?

[samzong]

@lmktfy After check the hugo changelog, These may be the reason we upgrade.

• 15+ Major Features Added, like JavaScript Bundle Groups and
• Performance & Build Improvements
• Memory usage optimization for large image sets (good for partners page)
• ...

[lmktfy]

What benefits do we, Kubernetes, get? (anyone can comment)

[AlexandrosMo]

i have the same error in hugo v0.147.9

[samzong]

For me.

As a contributor in k/website and k/sigs, I work on multiple projects.

However, I only install one version of Hugo on my local. when I switch between projects (e.g., from k/website to another project like k/kueue or etc that uses a different hugo version), I need to reinstall or switch environments, which is time-consuming and error-prone.

Just like the make serve issue encountered this time, I propose updating k/website to a more stable and compatible version.

specific benefits for the K8s community:

• Improved contributor efficiency: Reduces issues with environment setup, allowing more people to focus on content contributions (like documentation) rather than debugging tools—this is critical in the k8s community
• Reduced errors and maintenance overhead: The kind of issue we encountered is a common pain point.
• Community consistency: Similar to k8s best practices, this approach can influence more k/sigs and related projects.

Like k8s, we also recommend users to iterate their versions gradually to avoid the high upgrade costs caused by large version gaps—just like the current situation.

If... we can discuss how to select a Hugo version.