-
Notifications
You must be signed in to change notification settings - Fork 48
updating hugo to latest version (v0.105.0) #483
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updating hugo to latest version (v0.105.0) #483
Conversation
CGBassPlayer
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In my local testing:
- Development container was built
- Development container ran successfully
- Local E2E tests ran successfully
- Build Metrics ran successfully
- Production container built successfully
So this LGTM!
|
Looks like in the months this has been sitting, Hugo as gone all the way to v0.110.0. I will have to look through the releases and see if there is anything new we may want or if v0.105.0 is still good for us |
|
thanks @CGBassPlayer ! And @elreydetoda too... yes, lets get this updated if all looks good on the new version. |
|
BTW, for anyone that's interested I created a quick script to gather all the GH info for releases here. The first time I decided to read the changelog I created this, because I wasn't going to go and look at every release's full release notes manually 🙃 |
|
Here's the output from the tool: by running: If you drop the |
|
So, there'e actually some pretty cool stuff that was released for Hugo. Mainly the 0.110.0 & 0.109.0 releases. Specifically config.toml -> hugo.toml (0.110.0) I don't think we need any of that right now, but I'll create another issue for upgrading later on, mainly just want to get this merged so @CGBassPlayer can do the 404 testing stuff. (attaching for next issue) |
want to upgrade hugo to the latest version, mainly because of this feature we need: #475 (comment)
@gerbrent, don't know if we need to pull in @ironicbadger for this but the new container should just build (without any issues) and the deploy steps should be the exact same. So, I think it'll be fine to just merge this and let his build pipeline handle the rest. 😁
here is an md file which has the changelog for all the changes between the versions.
summary.md