Bump Hugo & other dependencies about prow HOT 9 CLOSED

I just noticed that Mermaidjs diagrams are not working locally. I think updating Hugo might help here.

EDIT: I don't think upgrading Hugo is related to this. This might be an issue related to my local install of Hugo and Docsy. The main reason is because AFAICS both my local and our production version uses Mermaid 9.2.2 and it doesn't make sense that it only fails locally for me when they're on the same version. Just clarifying for the record...

I think the bigger priority is probably getting a containerized version of the build system. The only downside here is that there could be a mismatch between this container and what Netlify uses. I'm not sure what the best practice is here.

from prow.

We should probably do something similar to what k/w does wrt grepping the Hugo version so that the container closely matches whatever Netlify uses.

WRT kubernetes/website#34794 I see that they just check in the actual MermaidJS source code directly into a static asset folder. I'm not sure about this (although I don't have strong opinions either way).

from prow.

I've updated some dependencies as part of #35 (notably Docsy to 0.6.0).

Not sure if we need to bump Hugo itself. WDYT @jihoon-seo ?

from prow.

Like all other dependencies, upgrading Hugo is not a mandatory thing, but seems to be a good thing to do.. 🙂

Notable new features of Hugo v0.101.0:

• indentation fixes to shortcode blocks
• resources.Copy function
• improved error handling

from prow.

The only downside here is that there could be a mismatch between this container and what Netlify uses. I'm not sure what the best practice is here.

k/w case:

• Hugo version for Netlify (preview & prod) is configured in netlify.toml, which this repo also has.
• In Makefile, that Hugo version is extracted from netlify.toml with grep
• In some Makefile rules that run container, use the extracted Hugo version as a part of container image tag, which in turn is pulled and run.

About Mermaid.js,
there had been issues that Mermaid diagrams were not displayed correctly,
and AFAIK this has been fixed by some PR.
Please see kubernetes/website#34794, and some other issues & PRs if needed.

from prow.

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle stale

from prow.

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

This bot triages un-triaged issues 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 issue is closed

You can:

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

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

/lifecycle rotten

from prow.

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

This bot triages issues 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 issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

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

/close not-planned

from prow.

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

from prow.