fix: Deprecates and windows filename restrictions #812
Merged
Conversation
Contributor
|
👍 All image files/references (if any) are in webp format, in line with our policy. |
Contributor
📝 Spell Check ResultsFound 1 potential spelling issue(s) when checking 43 changed file(s): 📄
|
| Line | Issue |
|---|---|
| 157 | Compleat ==> Complete |
ℹ️ How to address these issues:
- Fix the typo: If it's a genuine typo, please correct it.
- Add to whitelist: If it's a valid word (e.g., a name, technical term), add it to
.codespell-ignore.txt - False positive: If this is a false positive, please report it in the PR comments.
🤖 This check was performed by codespell
Contributor
|
✅ Staging Deployment Status This PR has been successfully deployed to staging as part of an aggregated deployment. Deployed at: 2026-06-24 20:30:34 UTC The staging site shows the combined state of all compatible open PRs. |
richarddushime
changed the title
LukasWallrich
approved these changes
Jun 24, 2026
LukasWallrich
left a comment
LukasWallrich
left a comment
Contributor
There was a problem hiding this comment.
Thanks! Good to get this updated
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Trailing periods in tags — Four curated resource files had tags like "Statistics." or "Methodological Reform." with a period at the end. Hugo turns tags into URL paths, and Windows forbids folder/file names ending with a period. Removed the trailing periods from all four tags.
Deprecated _build front matter — Two files used _build: which Hugo removed in v0.145.0. Renamed to build: which is the current key.
Why it only breaks on Windows:
macOS and Linux filesystems allow directory names ending with ., so the site builds fine there. Windows (NTFS) silently strips or rejects trailing periods in paths, causing Hugo to error out. The fix is cross-platform safe — removing a trailing period from a tag doesn't affect anything on macOS/Linux either.
additionally the deprecation fixes:
.Site.LanguageCode → site.Language.Locale (deprecated Hugo v0.158.0)
Type of Change
Testing
Checklist
Notes