-
Notifications
You must be signed in to change notification settings - Fork 710
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.0.0 #1510
base: main
Are you sure you want to change the base?
Release 4.0.0 #1510
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops .. should be 4.0.0
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm with PR title updated.
Updated the tile. I'll wait for the tests to land it though. |
Hm, the failures on the test-bazel runners look like they might be some kind of real issue. Maybe @walkingeyerobot has an idea what's happening? |
03f3e2f
to
ae7ca15
Compare
Actually it looks like the node version being used it too old so it doesn't support |
Maybe try updating node_version in bazel/emscripten_deps.bzl. I guess it would make sense to match the emsdk version: 20.18.0. Maybe add a comment to keep them in sync too. |
I suspect sbc is right and this will unblock here |
Rebasing should fix now. Is there some reason you revert the PR title? |
In fact I didn't revert the PR title. The bot force-pushed over my changes and reverted the PR title. I'm just going to run create_release.py manually and then close this. |
With emscripten-releases revisions:
https://chromium.googlesource.com/emscripten-releases/+/3ebc04a3dab24522a5bf8ced3ce3caea816558f6 (LTO)
https://chromium.googlesource.com/emscripten-releases/+/912ac2d711bb343205f314564ed287d883a7d888 (asserts)