Pin Netlify HUGO_VERSION to 0.48.1 to avoid Hugo install checksum failure

[FrancesCoronel]

Motivation

• Netlify builds were failing during dependency installation because hugo-extended@0.48 download produced a checksum mismatch; pinning a patch release prevents the installer from hitting the broken artifact path.
• Keep the Hugo major/minor line the same while moving to a known-good patch (0.48.1) to restore installs without broader changes.

Description

• Updated netlify.toml to set HUGO_VERSION = "0.48.1" in both the [context.production.environment] and [context.deploy-preview.environment] sections.
• Committed the change and prepared a PR that pins the Hugo patch version to avoid the failing hugo-extended@0.48 checksum path.

Testing

• Ran mise ls-remote hugo-extended which could not fetch remote releases from GitHub (remote fetch warnings), so remote resolution could not be fully validated. (Command completed with warnings.)
• Ran npm run build locally to sanity-check the change and confirm the repository reflects the updated netlify.toml, but the build failed in this environment due to unrelated local constraints (missing hugo binary, missing tailwindcss/plugins/container module, and missing Algolia env vars), so end-to-end build could not be completed here.

---

Codex Task

[netlify]

✅ Deploy Preview for apprenticeships ready!

Name	Link
🔨 Latest commit	2919ce2
🔍 Latest deploy log	https://app.netlify.com/projects/apprenticeships/deploys/699a0b9d1cb1e90008f7512a
😎 Deploy Preview	https://deploy-preview-666--apprenticeships.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 project configuration.