Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Upgrade default version of hugo #93
Our current default version of hugo is quite old - almost halfway back in the version history (v0.17 vs current v0.30.2).
Could we do the thing we've done with node wherein we pin the old version for old sites and install a newer version to use by default when someone uses a build command
It would be a better user experience as very few new customers showing up today use old hugo.
This would need an associated migration in the database for existing repo settings, and some logic in the build image to respect it, but this seems like the sanest place to track all the work.
Request by @bep and his posse of thousands of hugo users :)
referenced this issue
Nov 30, 2017
We will be updating this, but hugo will probably move faster than our update cycle. Because we don't want to be moving the cheese on a lot of people that aren't being specific about the version that they're using, we have to be careful about updating versions.
I'd recommend setting the
Yes that is what raised my question, because in Hugo docs it's said:
which made me think we are bound to Netlify's Hugo version. This was preventing me from using Netlify as I would like to benefit the latest Hugo versions, but it's awesome that we can use whatever version we want, thanks :)
Maybe the Hugo docs should be clarified in regard to this, I can try a PR if you want @gohugoio
@inwardmovement I'd suggest referring to this blog post that describes in depth what hugo versions are available on netlify and the two ways you can configure one: