release: 4.0.0

[curbengh]

What does it do?

Closes #3508 , Closes #3611

How to test

git clone -b 4.0.0 https://github.com/curbengh/hexo.git
cd hexo
npm install
npm test

Pending deps (in hexo):

• hexo-util@1
• hexo-front-matter@1
• hexo-log@1
• hexo-fs@2
• hexo-i18n@1
• hexo-renderer-marked@2
• hexo-cli@3
• warehouse@3

Pending deps' PR:

• hexo-util@1
• hexo-front-matter@1
• hexo-log@1
  • hexo-bunyan@2
• hexo-fs@2
• hexo-i18n@1
• hexo-generator-archive@1
• hexo-generator-category@1
• hexo-generator-index@1
• hexo-generator-tag@1
• hexo-renderer-ejs@1
• hexo-renderer-stylus@1
• hexo-renderer-marked@2
• hexo-server@1
• hexo-cli@3
  • hexo-fs@2
  • hexo-log@1
  • hexo-util@1
• warehouse@3

hexo-starter needs to be updated once this is merged but before publish.

[coveralls]

Coverage remained the same at 97.278% when pulling 6bf6e98 on curbengh:4.0.0 into 79bdc95 on hexojs:master.

[SukkaW]

• compare/3.9.0...master
• hexo docs v4 milestone

[curbengh]

Please only tick the checklist when the dep has been released (its release PR merged) and updated in hexo (update dep PR by dependabot merged).

Edit: I separated them into two checklists.

[yoshinorin]

@curbengh @SukkaW
Now, I'm suggesting use project board https://github.com/orgs/hexojs/teams/core/discussions/6
If you have some opinion, please comment to https://github.com/orgs/hexojs/teams/core/discussions/6

[tomap]

arcchive & category published
not sure what to do on hexo-log & hexo-bunyan ?

[curbengh]

I already emailed @NoahDragon about hexo-bunyan.

[tomap]

I just merged hexojs/hexo-starter@beb727c
However, it is directly used by hexo init command
So, if we stay like that, hexo init becomes compatible only with nodejs >= 8
Shall we rollback?

[SukkaW]

@tomap

Since hexojs/site#1026 has already be merged, I think it will be fine.

[curbengh]

Besides, all essential plugins (which drop node 6) are already published.

[curbengh]

All blocking bugs/PRs have been fixed/merged, so I think this is ready.

---

Rebased to make sure.

[SukkaW]

@curbengh Pending document update, there are some PRs are still in draft.

[curbengh]

you mean my PRs? Those are actually ready, I set it to draft to prevent being mistakenly merged (before v4).

Maybe we should prepare a release note in the meantime as well, I'll prepare it in these few days.

[SukkaW]

We should review all PRs listed in Post v4 project, make sure they will be fine to merged immediately after Hexo v4 released.

[yoshinorin]

🚀

[curbengh]

Blocking bug #3758

[curbengh]

I would like to include hexojs/hexo-util#110, but if the fix is not right (i.e. too ugly), I don't mind postponing it.

---

Edit: Postponing hexojs/hexo-util#110.

This is ready.

---

#3765

[curbengh]

Ready

[yoshinorin]

I think it's OK except for a few documentations :)

[curbengh]

https://www.npmjs.com/package/hexo/v/4.0.0

---

I also cleaned up the tags,

$ npm dist-tag rm hexo@1.2.4 stable
$ npm dist-tag rm hexo@3.2.0-beta.2 beta

[NoahDragon]

Congrats, it is a really big milestone after Hexo 3. It took four years to achieve this. Thank you all.