Update HUGO_VERSION to 0.128.2

[ydFu]

Bump Hugo version to 0.128.2.

ref: https://github.com/gohugoio/hugo/releases/tag/v0.128.2

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ydFu Once this PR has been reviewed and has the lgtm label, please assign mrbobbytables for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

[stmcginnis]

Looks like there are some issues to sort out:

4:14:44 AM: ERROR render of "page" failed: "/opt/build/repo/themes/docsy/layouts/blog/baseof.html:4:7": execute of template failed: template: blog/single.html:4:7: executing "blog/single.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:21:12: no such template "_internal/google_analytics_async.html"

There are also a couple errors and warnings due to argument deprecations.

[ydFu]

Looks like there are some issues to sort out:

4:14:44 AM: ERROR render of "page" failed: "/opt/build/repo/themes/docsy/layouts/blog/baseof.html:4:7": execute of template failed: template: blog/single.html:4:7: executing "blog/single.html" at <partial "head.html" .>: error calling partial: execute of template failed: html/template:partials/head.html:21:12: no such template "_internal/google_analytics_async.html"

There are also a couple errors and warnings due to argument deprecations.

I tried using npm install -g postcss-cli autoprefixer with git submodule update --init --recursive --depth 1 which failed to resolve the issue. Do you have any suggestions to solve it together?

ref:https://github.com/kubernetes/contributor-site?tab=readme-ov-file#natively

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale