Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

release: 4.1.0 #3896

Merged
merged 1 commit into from
Dec 9, 2019
Merged

release: 4.1.0 #3896

merged 1 commit into from
Dec 9, 2019

Conversation

curbengh
Copy link
Contributor

@curbengh curbengh commented Dec 1, 2019

What does it do?

How to test

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

Screenshots

Pull request tasks

  • Passed the CI test.

@curbengh curbengh added this to the v4.1.0 milestone Dec 1, 2019
@curbengh
Copy link
Contributor Author

curbengh commented Dec 1, 2019

@coveralls
Copy link

Coverage Status

Coverage remained the same at 97.128% when pulling a9335a6 on curbengh:4.1.0 into 2e0876e on hexojs:master.

@SukkaW
Copy link
Member

SukkaW commented Dec 1, 2019

I have approve those pending PRs. We can start working on documents.


I have bring up hexojs/site#1232 & hexojs/site#1233

@curbengh curbengh marked this pull request as ready for review December 1, 2019 09:47
@SukkaW
Copy link
Member

SukkaW commented Dec 1, 2019

The documents for #3681 & #3690 need update.

@curbengh
Copy link
Contributor Author

curbengh commented Dec 2, 2019

The documents for #3681 & #3690 need update.

hexojs/site#1234

@curbengh
Copy link
Contributor Author

curbengh commented Dec 6, 2019

#3908

@curbengh
Copy link
Contributor Author

curbengh commented Dec 7, 2019

@hexojs/core
I think we're good to go, this is getting long in the tooth.

Copy link
Member

@SukkaW SukkaW left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is ok to go.

@curbengh curbengh merged commit 979d1f4 into hexojs:master Dec 9, 2019
@curbengh curbengh deleted the 4.1.0 branch December 9, 2019 03:47
@curbengh
Copy link
Contributor Author

curbengh commented Dec 9, 2019

@Icecream-blue-sky
Copy link

I want to make sure that if I upgrade hexo 3.9.0 to 4.1.0, do I need to start over and configure my blog once again(I have done this for three times and I don't want a forth try!!).What should I do if I only want to upgrade hexo 3.9.0 to 4.1.0 and don't change any other things of my blog(since hexo 3.9.0 works well on my blog)?

@curbengh
Copy link
Contributor Author

For upgrade, you shouldn't need to reconfigure anything as we always make sure old config still work.

However, there might be some breaking change for theme. Let us know if you encounter any issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants