-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Time for a release candidate 4? #1476
Comments
is there an issue tracking the 1.0.0 release? What is left to be done? |
Here it is, @jessbowers-DSS: https://github.com/cheeriojs/cheerio/projects/1 |
@matthewmueller, @fb55 or @jugglinmike ? |
Thanks for the merging the PR @fb55! Would it be possible to push a new version to NPM too? |
Btw we can try to get rid of lodash |
I was thinking that just get security fixes out now, and then continue the work on final v1.0.0 without any hasty changes =) |
Seems it's going to be a bit more substantial stuff added to rc.4: #1499 (comment), @TrySound =) |
Published 1.0.0-rc.4! |
Wouldn't it be good to create a 1.0.0-rc.4 branch and publish to NPM? This way we could get the security updates even if 1.0.0 is not finished yet.
The text was updated successfully, but these errors were encountered: