fix not updated Internal version

[ljcbaby]

PR Checklist

• The commit message follows guidelines for NexT.
• Tests for the changes was maked (for bug fixes / features). Not needed
  • Muse | Mist have been tested.
  • Pisces | Gemini have been tested.
• Docs in NexT website have been added / updated (for features).

PR Type

• Bugfix.
• Feature.
• Code style update (formatting, local variables).
• Refactoring (no functional changes, no api changes).
• Documentation.
• Translation.
• Other... Please describe:

What is the current behavior?

Issue resolved: Updated the annotated Internal version which not updated in version 1f26b10

What is the new behavior?

• Link to demo site with this changes: null
• Screenshots with this changes: null

How to use?

In NexT _config.yml: null

[welcome]

Thanks so much for opening your first PR here!

[CLAassistant]

All committers have signed the CLA.

[stevenjoezhang]

Thanks for your contribution. However, Internal version means the version of files in this folder: https://github.com/next-theme/hexo-theme-next/tree/master/source/lib and it's not necessary to update the version.

See also #61 (comment)
https://theme-next.js.org/docs/advanced-settings#Core-Plugins

[ljcbaby]

So I should update the Internal files too?

[ljcbaby]

Thanks for your contribution. However, Internal version means the version of files in this folder: https://github.com/next-theme/hexo-theme-next/tree/master/source/lib and it's not necessary to update the version.

See also #61 (comment)
https://theme-next.js.org/docs/advanced-settings#Core-Plugins

For inconsistent versions, I have some obsessive-compulsive disorder

[stevenjoezhang]

Thanks very much! In fact I have some obsessive-compulsive disorder too 😂
It's time to make a choice:

1. Inconsistent versions
2. When a new version of any dependency packages is released, update these compressed / binary files, which is not very elegant in the Git commit history

Give me some time, I will think about whether there is a third way. There have been many discussions about how to manage NexT's dependency packages, e.g. using submodule or npm: theme-next/hexo-theme-next#663
The problem is that most users use git clone to install a Hexo theme, not npm install, so users need to execute additional commands after the theme installation.

[stevenjoezhang]

Superseded by #72