# Backport
This will backport the following commits from `main` to `8.13`:
- [Upgrade Node.js to 20.11.1
(#177042)](https://github.com/elastic/kibana/pull/177042)
<!--- Backport version: 9.4.3 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT
[{"author":{"name":"Jon","email":"jon@elastic.co"},"sourceCommit":{"committedDate":"2024-02-20T20:01:23Z","message":"Upgrade
Node.js to 20.11.1
(#177042)","sha":"37ae67a0a09878e9fa6c0a46f1455173d3a3401c","branchLabelMapping":{"^v8.14.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:Operations","release_note:skip","backport:prev-minor","v8.14.0"],"title":"Upgrade
Node.js to
20.11.1","number":177042,"url":"https://github.com/elastic/kibana/pull/177042","mergeCommit":{"message":"Upgrade
Node.js to 20.11.1
(#177042)","sha":"37ae67a0a09878e9fa6c0a46f1455173d3a3401c"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.14.0","branchLabelMappingKey":"^v8.14.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/177042","number":177042,"mergeCommit":{"message":"Upgrade
Node.js to 20.11.1
(#177042)","sha":"37ae67a0a09878e9fa6c0a46f1455173d3a3401c"}}]}]
BACKPORT-->
Co-authored-by: Jon <jon@elastic.co>
## Summary
The previous PR https://github.com/elastic/kibana/pull/161813 was
reverted due to the broken webpack config
eef1afcd59
---------
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Jon <jon@elastic.co>
We're seeing less than ideal reliability for our node downloads from the
official site on CI.
This uses our cache for downloading node distributions for development.
The checksums on our linux distributions have been updated due to using
our glibc 2.17 node build.
Used similarly to our distributions:
82024c240a/src/dev/build/tasks/nodejs/node_download_info.ts (L21)
This PR fixes the setup we have for the node_module mirrors vars that
are overriding and pointing into our middle cache. The previous
configuration was not working as intended as the env vars set globally
on CI never ended up in the bazel managed yarn install.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Bumps node.js to 18.17.0 (replacement for PR #144012 which was later
reverted)
As a result, these categorical additions were needed:
- `node` evocations will need the `--openssl-legacy-provider` flag,
wherever it would use certain crypto functionalities
- tests required updating of the expected HTTPS Agent call arguments,
`noDelay` seems to be a default
- `window.[NAME]` fields cannot be written directly
- some stricter typechecks
This is using our in-house built node.js 18 versions through the URLs
the proxy-cache. (built with
https://github.com/elastic/kibana-custom-nodejs-builds/pull/4)
These urls are served from a bucket, where the RHEL7/Centos7 compatible
node distributables are. (see:
https://github.com/elastic/kibana-ci-proxy-cache/pull/7)
Further todos:
- [x] check docs wording and consistency
- [ ] update the dependency report
- [x] explain custom builds in documentation
- [x] node_sass prebuilts
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
Co-authored-by: Thomas Watson <w@tson.dk>
* Bazel config maintenance
- Removes node.js s390x - not a supported platform
- Updates the list of ignored bazel folders
- Updates yarn to 1.22.19, we're on a 2.5 year old version
* bump yarn in package.json
* chore(NA): upgrade bazel into v5
* chore(NA): initial work to upgrade to rules v5
* chore(NA): remove @elastic/datemath jest unit test for eslint plugin imports
* chore(NA): removed packager tsc_wrapped added my mistake
* chore(NA): redesign integration between bazel node_modules management and yarn kbn commands
* fix(NA): remove .yarn-integrity on force install
* fix(NA): include clean on force install
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* chore(NA): add warnings both to run and watch commands about Bazel built packages
* chore(NA): add new commands to build and watch bazel packages
* docs(NA): add documentation about how to deal with bazel packages
* chore(NA): addressed majority of the feedback received except for improved error logging
* chore(NA): disable ibazel info notification.
* chore(NA): remove iBazel notification
* chore(NA): remove iBazel notification - kbn pm dist
* chore(NA): move show_results option to kbn-pm only
* chore(NA): patch build bazel command to include packages target list
* chore(NA): add pretty logging for elastic-datemath
* chore(NA): remove double error output from commands ran with Bazel
* fix(NA): include simple error message to preserve subprocess failure state
* docs(NA): missing docs about how to independentely watch non bazel packages
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>