Easy way to upgrade from an old version #3225
-
|
Hello everyone, First of all, I want to express my sincere gratitude to the entire community for developing and maintaining this fantastic tool. I have been using it for several years to build and manage my personal website, and I am truly grateful for all the effort that goes into it. Lately, I've been facing a challenge when it comes to updating my website. I've noticed that the templates are updated very frequently, which is great for introducing new features and improvements. However, this rapid pace of updates often introduces breaking changes that make the upgrade process quite difficult. The official guide suggests that upgrading should be as simple as updating the I was wondering if other members of the community have encountered similar issues. If so, I would be very interested to learn about your strategies for handling these kinds of breaking changes and managing the migration process. Any advice or shared experiences would be greatly appreciated. Although there have been an existing discussion. I really don't feel that manually copying & checking building is a good choice... See the comment. There are many reasons. The situation for me is like:
By the way, the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hello, |
Beta Was this translation helpful? Give feedback.
Hugo is growing and Hugo team regularly make breaking changes, so if you have an old version, there will likely be many breaking changes to apply from the release notes on Hugo's Github.
As per the docs, if your site is really old, users typically find it easier to start fresh with the latest version of their site's template and gradually migrate their content across - then the effort to upgrade is minimal as it's just moving your content and site metadata across to the latest version.
If you don't …