-
Notifications
You must be signed in to change notification settings - Fork 522
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
chore: update NodeJS to LTS 12.13.0 and yarn to 1.19.1 version #1313
chore: update NodeJS to LTS 12.13.0 and yarn to 1.19.1 version #1313
Conversation
for extensionless imports nearest parent package.json should contain a top-level field "type": https://nodejs.org/docs/latest-v12.x/api/esm.html#esm_enabling
let's just pin that protocol buffers example back to v10 if it's not trivial to fix it, so we can roll this out. Thanks! |
Looks like that one could be solved by upgrading dependencies for |
jsdoc peer dependency `requizzle` is failing due to this: hegemonic/requizzle#6
FYI I mirrored the four new files to the bazel-mirror URL |
Failure is
looks like the action wants to write to the node_modules which is probably a read-only filesystem. Do you know what we need to install to prevent protobufjs doing this? |
Issue is that I don't know how to deal with it yet |
… 6.8.8 deps in other case protobuf.js will try to npm install mismatched dependency versions programmatically and fail due to read-only sandbox fs: https://github.com/protobufjs/protobuf.js/blob/69623a91c1e4a99d5210b5295a9e5b39d9517554/cli/util.js#L129 https://github.com/protobufjs/protobuf.js/blob/69623a91c1e4a99d5210b5295a9e5b39d9517554/package.json
other dependencies here should have the same major version as in protobufjs package.json
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.
thank you for getting it green!
PR Type
What kind of change does this PR introduce?
Node version bump to current LTS.
Does this PR introduce a breaking change?
Builds not compatible with Node 12 could fail.
Builds relying on native dependencies in case if binaries for NODE_MODULE_VERSION=72 are not yet published for such dependency, will definitely fail (
bcrypt
, etc.).Solution for such builds is quite straightforward though: use specific Node version in
node_repositories
definition inWORKSPACE
file: