Update extension gitlab workflow node version (#13032)

* Update node and yq versions for extension gitlab workflow

* Add warning for gitlab workflow target branch

docusaurus/docs/extensions/publishing.md

@@ -205,6 +205,29 @@ When building an extension that will be housed in a GitLab repository or hosted
 This pipeline will build an ECI and publish it to container registry (`registry.gitlab.com` by default) to allow for importing into Rancher Manager.
 The actual pipeline jobs are defined in the [Dashboard repo](https://github.com/rancher/dashboard/blob/master/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml) to allow for proper versioning and to apply any updates to the pipeline without any additional work from the Extension developer.
 
+> **_WARNING:_** Ensure the branch of `rancher/dashboard` in the `remote` url containing the reusable workflow matches the release version of your `@rancher/shell` npm dependency. For example:
+> - If building for the latest version of Rancher:
+> ```yaml
+> #.gitlab-ci.yml
+> ...
+> include:
+> - remote: 'https://raw.githubusercontent.com/rancher/dashboard/master/shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml'
+> ```
+> - If building for Rancher `v2.9`:
+> ```yaml
+> #.gitlab-ci.yml
+> ...
+> include:
+> - remote: 'https://raw.githubusercontent.com/rancher/dashboard/release-2.9/shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml'
+> ```
+> - If building for Rancher `v2.8`:
+> ```yaml
+> #.gitlab-ci.yml
+> ...
+> include:
+> - remote: 'https://raw.githubusercontent.com/rancher/dashboard/release-2.8/shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml'
+> ```
+
 ### Pipeline Configuration
 
 There are a few pipeline configuration options, mostly tied to the container registry:

docusaurus/extensions_versioned_docs/version-v2/publishing.md

@@ -205,6 +205,22 @@ When building an extension that will be housed in a GitLab repository or hosted
 This pipeline will build an ECI and publish it to container registry (`registry.gitlab.com` by default) to allow for importing into Rancher Manager.
 The actual pipeline jobs are defined in the [Dashboard repo](https://github.com/rancher/dashboard/blob/master/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml) to allow for proper versioning and to apply any updates to the pipeline without any additional work from the Extension developer.
 
+> **_WARNING:_** Ensure the branch of `rancher/dashboard` in the `remote` url containing the reusable workflow matches the release version of your `@rancher/shell` npm dependency. For example:
+> - If building for Rancher `v2.9`:
+> ```yaml
+> #.gitlab-ci.yml
+> ...
+> include:
+> - remote: 'https://raw.githubusercontent.com/rancher/dashboard/release-2.9/shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml'
+> ```
+> - If building for Rancher `v2.8`:
+> ```yaml
+> #.gitlab-ci.yml
+> ...
+> include:
+> - remote: 'https://raw.githubusercontent.com/rancher/dashboard/release-2.8/shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml'
+> ```
+
 ### Pipeline Configuration
 
 There are a few pipeline configuration options, mostly tied to the container registry:

shell/scripts/.gitlab/workflows/build-extension-catalog.gitlab-ci.yml

@@ -1,7 +1,7 @@
 variables:
-  NODE_VERSION: "v16.20.2"
+  NODE_VERSION: "v20.17.0"
   NODE_DISTRO: "node-${NODE_VERSION}-linux-x64"
-  YQ_VERSION: "v4.44.1"
+  YQ_VERSION: "v4.44.6"
   YQ_URL: "https://github.com/mikefarah/yq/releases/download/${YQ_VERSION}/yq_linux_amd64"
 
 .podman-setup: &podman-setup