mirror of
https://github.com/elastic/kibana.git
synced 2025-04-23 17:28:26 -04:00
# Backport This will backport the following commits from `main` to `8.9`: - [[docs] Improve Node.js upgrade docs (#163268)](https://github.com/elastic/kibana/pull/163268) <!--- Backport version: 8.9.7 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Thomas Watson","email":"watson@elastic.co"},"sourceCommit":{"committedDate":"2023-08-07T20:08:18Z","message":"[docs] Improve Node.js upgrade docs (#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808","branchLabelMapping":{"^v8.10.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport:all-open","v8.10.0"],"number":163268,"url":"https://github.com/elastic/kibana/pull/163268","mergeCommit":{"message":"[docs] Improve Node.js upgrade docs (#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v8.10.0","labelRegex":"^v8.10.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/163268","number":163268,"mergeCommit":{"message":"[docs] Improve Node.js upgrade docs (#163268)","sha":"7ff43da2262ebcbd53d4e79ec496dc2ec9b3e808"}}]}] BACKPORT--> Co-authored-by: Thomas Watson <watson@elastic.co>
This commit is contained in:
parent
dcca7c8054
commit
0fe9603705
1 changed files with 10 additions and 4 deletions
|
@ -37,15 +37,21 @@ Use best judgement when backporting.
|
|||
|
||||
==== Node.js patch upgrades
|
||||
|
||||
Typically, you want to backport Node.js *patch* upgrades to all supported release branches that run the same *major* Node.js version (which currently is all of them, but this might change in the future once Node.js v18 is released and becomes LTS):
|
||||
Typically, you want to backport Node.js *patch* upgrades to all supported release branches that run the same *major* Node.js version (which currently is all of them, but this might change in the future):
|
||||
|
||||
- If upgrading Node.js 16, and the current release is 8.1.x, the main PR should target `main` and be backported to `7.17` and `8.1`.
|
||||
- If the current release is 8.1.x, the main PR should target `main` and be backported to `7.17` and `8.1` (GitHub tag example: `backport:all-open`).
|
||||
|
||||
==== Node.js minor upgrades
|
||||
|
||||
Typically, you want to backport Node.js *minor* upgrades to the next minor {kib} release branch that runs the same *major* Node.js version:
|
||||
Typically, you want to backport Node.js *minor* upgrades to the previous major {kib} release branch (if it runs the same *major* Node.js version):
|
||||
|
||||
- If upgrading Node.js 16, and the current release is 8.1.x, the main PR should target `main` and be backported to `7.17`, while leaving the `8.1` branch as-is.
|
||||
- If the current release is 8.1.x, the main PR should target `main` and be backported to `7.17`, while leaving the `8.1` branch as-is (GitHub tag example: `auto-backport` + `v7.17.13`).
|
||||
|
||||
==== Node.js major upgrades
|
||||
|
||||
Typically, you want to backport Node.js *major* upgrades to the previous major {kib} release branch:
|
||||
|
||||
- If the current release is 8.1.x, the main PR should target `main` and be backported to `7.17`, while leaving the `8.1` branch as-is (GitHub tag example: `auto-backport` + `v7.17.13`).
|
||||
|
||||
=== Upgrading installed Node.js version
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue