Fix deployment by updating the Hugo version (#44)

Summary

The GitHub Pages deployment has failed on every push to main since PR #40. That PR bumped Hugo to 0.160.1 in netlify.toml and bumped the PaperMod pin in go.mod, but the Pages workflow was left at HUGO_VERSION: 0.128.0. The newer theme requires Hugo 0.146.0 or greater, so Netlify and local builds stayed green while Pages broke.

From the most recent failing run:

WARN  Module "github.com/adityatelange/hugo-PaperMod" is not compatible with this Hugo version: Min 0.146.0
ERROR => hugo v0.146.0 or greater is required for hugo-PaperMod to build
ERROR render of "404" failed: ... partial "head.html" not found
Error: error building site: render: failed to render pages: render of "home" failed ...

The old Hugo can’t read the new theme’s layout structure, so every page fails on the missing head.html partial.

Changes

.github/workflows/hugo.yaml: HUGO_VERSION 0.128.0 to 0.160.1, matching netlify.toml.

Verification

hugo --gc --minify builds clean from this branch: 71 pages, no errors (only pre-existing .Language.LanguageDirection / .Language.LanguageCode deprecation warnings from the theme).
Confirmed the release asset the workflow downloads exists: hugo_extended_0.160.1_linux-amd64.deb returns HTTP 200.
The Pages run on this PR is the real check, since the workflow only triggers on pushes to main.

Python Documentation Editorial Board

This repo contains activity updates, process, and planning information for the Python Documentation Editorial Board.

See PEP 732.

Changelog

We have a “changelog” of decisions: changelog directory.

Updates

Read updates of the Editorial Board’s activities. Subscribe to the updates using the RSS feed.

Process

The Editorial Board’s private meetings are monthly on the second Tuesday at 1:30pm Pacific.

If you have a general request or question, please use the Documentation category in Discourse.

If you need Editorial Board assistance, please file an issue on this repo.

Reference

These links give context on the editorial board:

These links give context on existing documentation landing pages:

Writing new content

Hugo is not needed to be installed in order to write a new meeting minutes.

Write the meeting minutes a markdown file under content/updates/*.md, commit, and create the pull request. A preview will then be generated on Netlify.

The meeting minutes should be written using template provided in archetypes/updates.md.

If you have Hugo installed, a new meeting minutes file can be created by typing on the command line:

hugo new content content/updates/newupdate.md

This will create the file under content/updates/newupdate.md, and you can continue editing it.

(replace “newupdate.md” with the desired filename.)

Updating the Meeting Attendee List

The list of attendees is pulled from the "members" field in the frontmatter. By default, it lists all members of the Python Docs Editorial Board. If a member did not attend the meeting, remove from this list.

Building the static site locally

First install Hugo.
Run the command at the root of the repository:

hugo server

Writing new changelog

Use the template in archetypes/changelog.md.

The file can also be created using the command:

hugo new content content/changelog/newchangelog.md

It will create a new file under content/changelog/newchangelog.md. (Replace “newchangelog.md” with the desired filename).