Hexo 6.0.0

[tomap]

Following the breaking change on list_tags, I propose to release a v6 of Hexo
cf 042f862

I checked, and this was the only commit to release v5: 1489074

I would also suggest to update all dependencies that are not yet updated before releasing v6 (devDependencies)

Anyone wanted to add something to the v6 ?

We should also prepare a blog post to announce the release :)

[coveralls]

Coverage decreased (-0.1%) to 98.147% when pulling 7b6b804 on hexo-6 into 042f862 on master.

[yoshinorin]

How about drop Node 10.x?

#4378

IMHO we should start to drop Node.js 10.x from all repos.

[SukkaW]

I will mark this pr as a proposal. Obviously, it is an opportunity for us to introduce many other breaking changes as well.

[SukkaW]

I will mark this pr as a proposal. Obviously, it is an opportunity for us to introduce many other breaking changes as well.

FYI, I am currently working on replacing RegExp with the state machine for escaping (in backtickcode filter and in post render).

[tomap]

Ideally, if we could do this release before Sept 18th, that would be great :)

[stevenjoezhang]

I would suggest to migrate from commonjs to esm in Hexo 6. All dependency packages created by Sindre Sorhus require esm to load.

[tomap]

@stevenjoezhang I also think we should do that, but this project will clearly take longer than Sept 18th, so I would recommend doing that in Hexo 7

[stevenjoezhang]

OK, I replied here as a to-do list #4378 (comment)

[SukkaW]

I will mark this pr as a proposal. Obviously, it is an opportunity for us to introduce many other breaking changes as well.

FYI, I am currently working on replacing RegExp with the state machine for escaping (in backtickcode filter and in post render).

#4780

[SukkaW]

Some other PRs and proposals I'd like to include in the Hexo 6.0.0:

• feat: load hexo plugin in the theme's package.json #4771
• fix(#1490): if post_asset_folder is set, restrict renderable files to default file extension #4781
• [Proposal] Use memoize in our helper and util function  #4782
• fix(url_for): absolute path is processed by relative_url hexo-util#262

[tomap]

Could we create v6.0, even without #4781 that would allow us to have a fix for the security issue released recently

[SukkaW]

Could we create v6.0, even without #4781 that would allow us to have a fix for the security issue released recently

I have already made an announcement about the CVE: #4838

But yeah, I'd like to have 6.0.0 released ASAP.

Also, we need to address some kind of breaking changes migration guideline for the fix.

[yoshinorin]

@tomap @SukkaW
Should we merge this PR and release the v6.0.0?
Sorry, I don't know we should publish it or not...

If yes, I can publish a new version.

[tomap]

I'm ok with it. We need to prepare an announcement on site also? Before?

[yoshinorin]

I'm ok with it. We need to prepare an announcement on site also? Before?

I think after is enough.

[yoshinorin]

@hexojs/core
Done.
I just published the new version.

https://www.npmjs.com/package/hexo/v/6.0.0
https://github.com/hexojs/hexo/releases/tag/6.0.0

[yoshinorin]

Also, we need to address some kind of breaking changes migration guideline for the fix.

Does someone please let me know about migration guideline?
Or would you please edit v6.0.0 release note?