-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
deps: update V8 to 4.6.85.28 #3484
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Technically LGTM but if I read it right, this changes date parsing back from ES6 conforming to ES5. I understand that for Chromium not breaking the web is important but for us though, it's arguably a semver-major change... |
I understand that the change appeared with v8 4.6 so we don't have any release with it yet. |
This is why I think it's important to update before releasing v5.0.0. |
Oh hah, good point. Never mind I said that. EDIT: Double-checked that the change is not in 4.5 and it's not. |
This update fixes a breaking regression in the date parser. Ref: https://code.google.com/p/chromium/issues/detail?id=539813 Ref: https://code.google.com/p/chromium/issues/detail?id=543320 PR-URL: nodejs#3484 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
Landed in 6456fcf. |
This update fixes a breaking regression in the date parser. Ref: https://code.google.com/p/chromium/issues/detail?id=539813 Ref: https://code.google.com/p/chromium/issues/detail?id=543320 PR-URL: #3484 Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
This update fixes a breaking regression in the date parser.
Ref: https://code.google.com/p/chromium/issues/detail?id=539813
Ref: https://code.google.com/p/chromium/issues/detail?id=543320
cc @nodejs/v8