I maintain a documentation site, that has the following content:
content/
└── release-notes/
├── _index.md
├── stable-1.1.0.md
├── stable-1.2.0.md
└── stable-1.3.0.md
In 0.145.0, the content is rendered as:
release-notes/
├── index.html
├── stable-1.1.0/
│ └── index.html
├── stable-1.2.0/
│ └── index.html
└── stable-1.3.0/
└── index.html
In 0.146+, the content is rendered as:
release-notes/
├── index.html
└── stable-1
└── index.html
As you can see, the version in the file name is being treated as a file type.
Is this a bug? If not, what’s the cleanest way to fix my content to preserve the urls in 0.146+?
This is a known breaking change in v0.146.0:
https://github.com/gohugoio/hugo/issues/13515
You’ll have to do something like:
hugo new releases/v1-234-5.md
…then modify the slug
(optional) and title
.
Thanks for confirming this in intentional, and the best way to deal with it.
1 Like
This will break a lot of our current internal links and URLs. But then, I have to remember Hugo is still in beta (the v 0) hence our team will be sticking with version 0.145.0 for the coming few years.
It would be helpful to see a few example content paths.
system
Closed
April 16, 2025, 8:15pm
6
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.