Update hugo to 0.115.4

[jarrodmillman]

DO NOT MERGE UNTIL UPDATED TRANSLATIONS ARE MERGED

Depends on #639. See #649 (review).

Updating hugo in preparation for updating the theme. There were some changes in hugo 0.112 that are causing issues (addressed in e749f62) : https://gohugo.io/content-management/multilingual/#changes-in-hugo-01120

[netlify]

✅ Deploy Preview for numpy-org ready!

Name	Link
🔨 Latest commit	6e686ab
🔍 Latest deploy log	https://app.netlify.com/sites/numpy-org/deploys/64c45a76dca30900082709af
😎 Deploy Preview	https://deploy-preview-649--numpy-org.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[rgommers]

Thanks @jarrodmillman. These changes all seem useful, but I'd like to make sure that they won't cause problems for the imminent launch of the translated version of the site. We now have fully complete translations, and it seems to me that this may cause significant rework (not sure, I'm hoping @steppi can tell).

If there is a conflict, I'd much prefer to launch the Japanese and Portuguese translations first (should happen very soon), and then rebase this PR on top.

[steppi]

If there is a conflict, I'd much prefer to launch the Japanese and Portuguese translations first (should happen very soon), and then rebase this PR on top.

This branch, hugo-0.114.1, conflicts with the branch l10n_main, containing the updated translations. The conflict is in the files content/ja/config.yaml, content/ja/tabcontents.yaml, content/pt/config.yaml, and content/pt/tabcontents.yaml. As far as I can tell the changes are just a matter of formatting, though there was also some weirdness with duplicate entries.

Currently, l10n_main doesn't build with hugo 0.114.1. I suppose that should be expected @jarrodmillman, and the formatting will need to be updated?

I created a copy of l10n_main and tried to rebase it on hugo-0.114.1, make an effort to resolve the conflicts. When done, I was unable to build the page. I likely made a careless mistake that broke the formatting. The issue though is that Crowdin sometimes isn't very smart about preserving translations when there are updates on main. I'm concerned that if this goes in before the translations, the above files may need to be re-translated.

I think we should launch the translations first; it should be done this week. After that we can update hugo.

[steppi]

I hadn't attempted to build this PR branch locally until just now. I made sure hugo 0.114.1 was installed. The rendered page only includes a top bar with a link to the news page. I've just checked the deploy preview. The same issue appears there as well.

[stefanv]

Hugo 0.114 is forcing us to list non-standard parameters for each language under a params section. If the rendering is incomplete, it sounds like we also need to update the theme to pick up those values from a different location. EDIT: I just checked, and the theme already correctly uses Site.Params to access language-specific parameters.

I think we'll go ahead and fix the theme for now, and then when NumPy is ready (after the language merge?) we can just move the relevant sections under lang: params: ... and update the theme.

I will push a fix to the branch to make the site render correctly.

[steppi]

@jarrodmillman, updated translations are in now.

[stefanv]

@steppi I hope I managed to preserve all the translation updates!
@jarrodmillman This should now be good to go.

[steppi]

Looks good. The rendered output for Portuguese and Japanese looks right to me just by comparing with what was there previously, @melissawm @AtsushiSakai. The formatting changes might cause Crowdin to lose translations for the translated yaml files, but if so, I know how to fix that.

[stefanv]

@steppi If you are happy with this PR, please go ahead and merge it. I'm hesitant, since it may impinge on your work.

[stefanv]

Specifically, the structure of the config.yaml in #639 will be affected. But the update is also simple.

[stefanv]

Thanks, let me know if you need a hand in fixing up the others!

[steppi]

Thanks @stefanv. I'm pretty sure this won't cause problems