Skip to content

Hexo version migration

Hexo version migration refers to the process of updating the Hexo static site generator to a new version, which often requires verifying configuration files and ensuring necessary dependencies are installed to maintain functionality^[600-developer-blog-hexo-blog-update-hexo.md].

Key Considerations

When updating Hexo, particular attention must be paid to the project's settings. The _config.yml configuration file is a critical component that often requires review or modification during version updates to ensure compatibility with the new release^[600-developer-blog-hexo-blog-update-hexo.md].

Common Fixes

After an update, certain site features may break or behave unexpectedly due to missing renderers or deployers.

  • Git Deployment: To enable automatic deployment via Git (often used in conjunction with GitHub Actions), the hexo-deployer-git plugin must be installed^[600-developer-blog-hexo-blog-update-hexo.md].
  • Image Rendering: A common issue following an update is the disappearance of images. This is typically resolved by installing the hexo-renderer-marked plugin^[600-developer-blog-hexo-blog-update-hexo.md].

Automation

The deployment process can be automated using GitHub Actions workflows. For example, a workflow file located at .github/workflows/node.js.yml can be configured to handle the automatic deployment of the blog^[600-developer-blog-hexo-blog-update-hexo.md].

Sources

^[600-developer-blog-hexo-blog-update-hexo.md]