chore: prepare to move up to 1.10 in main branch; replace hardcoded 1.9 refs (#2064)

* chore: move up to 1.10 in main branch; replace hardcoded 1.9 refs

Signed-off-by: Nick Boldt <nboldt@redhat.com>

* revert to ocp 4.21 for links

Signed-off-by: rhdh-bot service account <rhdh-bot@redhat.com>

* replace hardcoded links with /latest/ to resolve obsolete (1.8, 1.9) and future 1.10 links before we're ready to branch

Signed-off-by: rhdh-bot service account <rhdh-bot@redhat.com>

* switch back to 1.9 until we branch

Signed-off-by: rhdh-bot service account <rhdh-bot@redhat.com>

---------

Signed-off-by: Nick Boldt <nboldt@redhat.com>
Signed-off-by: rhdh-bot service account <rhdh-bot@redhat.com>
Co-authored-by: rhdh-bot service account <rhdh-bot@redhat.com>

Author: nickboldt

artifacts/attributes.adoc

@@ -16,27 +16,29 @@
 :product-local: Red Hat Developer Hub Local
 :product-local-very-short: RHDH Local
 :product-version: 1.9
-:product-bundle-version: 1.9.0
-:product-chart-version: 1.9.0
+// TODO change to 1.10 when we create the release-1.10 branch
+// :product-version: 1.10
+:product-bundle-version: 1.10.0
+:product-chart-version: 1.10.0
 :product-backstage-version: 1.45.3
-:product-version-next: 1.10
+// after 1.10 we skip to 2.1
+:product-version-next: 2.1
 :product-custom-resource-type: Backstage
 :product-docs-url: https://docs.redhat.com/en/documentation/red_hat_developer_hub
 :product-docs-link: link:{product-docs-url}/{product-version}
 :backstage: Backstage
 // Minimum and current latest supported versions
 :ansible-automation-platform-version: 2.6
 :keycloak-version: 26.0
-// k8s and OCP min versions are aligned (OCP 4.16 is based on k8s 1.29)
-// when we drop support for 4.16, this moves to 1.31
-:kubernetes-version: 1.29
-:ocp-version-min: 4.16
-:ocp-version: 4.20
+// k8s and OCP min versions are aligned (OCP 4.18 is based on k8s 1.31)
+:kubernetes-version: 1.31
+:ocp-version-min: 4.18
+:ocp-version: 4.21
 :osd-version: 4
 :rhoserverless-version: 1.37.1
 :rhoserverless-version-major: 1.37
 :rhoserverless-logic-version: 1.37.2
-:orchestrator-plugin-version: 1.9.0
+:orchestrator-plugin-version: 1.10.0
 
 // Support levels
 :developer-preview: Developer Preview

artifacts/snip-tag-for-OCI-package-paths.adoc

@@ -1,11 +1,11 @@
-:_mod-docs-content-type: SNIPPET 
+:_mod-docs-content-type: SNIPPET
 
 The `<tag>` variable is your {product-very-short} application{apos}s version of {backstage} and the plugin version, in the format: `bs_<backstage-version>__<plugin-version>` (note the double underscore delimiter).
 
 * To find the correct image tag for `<tag>`:
-.. Look in the link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.9/html/red_hat_developer_hub_release_notes/pr01[{product-very-short} release notes preface] for your {backstage} version.  
-.. Locate the plugin version for paths starting with `oci://ghcr.io` within one of the tables in the {dynamic-plugins-reference-book-link}[Dynamic Plugins Reference guide].  
+.. Look in the link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/latest/html/red_hat_developer_hub_release_notes/pr01[{product-very-short} release notes preface] for your {backstage} version.
+.. Locate the plugin version for paths starting with `oci://ghcr.io` within one of the tables in the {dynamic-plugins-reference-book-link}[Dynamic Plugins Reference guide].
 
 For example, because {product-very-short} 1.9 is based on {backstage} 1.45.3, the tag will have the format `bs_1.45.3__<plugin-version>`.
 
-include::snip-tag-for-sha256-tip.adoc[]
+include::snip-tag-for-sha256-tip.adoc[]

modules/extend_orchestrator-in-rhdh/proc-install-rhdh-with-orchestrator-in-a-fully-disconnected-ocp-environment-using-the-helm-chart.adoc

@@ -26,7 +26,7 @@ mirror:
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@_<digest>_
-  
+
   helm:
     repositories:
       - name: openshift-charts
@@ -71,9 +71,9 @@ unpack () {
   cd $DIR; tree -d -L 3 -I "usr|root|buildinfo"
 }
 
-unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
+unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:{product-version}"
 
-# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_1.9/dynamic-plugins.default.yaml
+# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_{product-version}/dynamic-plugins.default.yaml
 ----
 
 . Mirror the images in the `ImageSetConfiguration.yaml` file by running the `oc-mirror` command. For example:
@@ -209,9 +209,9 @@ unpack () {
   cd $DIR; tree -d -L 3 -I "usr|root|buildinfo"
 }
 
-unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
+unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:{product-version)"
 
-# you can then find the dynamic-plugins.default.yaml under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_1.9/dynamic-plugins.default.yaml
+# you can then find the dynamic-plugins.default.yaml under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_{product-version)/dynamic-plugins.default.yaml
 ----
 
 .Verification
@@ -223,4 +223,4 @@ unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
 [NOTE]
 ====
 The successful accessibility of the Orchestrator UI confirms that the underlying components are running and the cluster recognizes the plugin.
-====
+====

modules/extend_orchestrator-in-rhdh/proc-install-rhdh-with-orchestrator-in-a-fully-disconnected-ocp-environment-using-the-operator.adoc

@@ -30,7 +30,7 @@ mirror:
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@_<digest>_
-  
+
   operators:
     - catalog: registry.redhat.io/redhat/redhat-operator-index:v<ocp-version>
      # For example: registry.redhat.io/redhat/redhat-operator-index:v{ocp-version}
@@ -66,9 +66,9 @@ unpack () {
   cd $DIR; tree -d -L 3 -I "usr|root|buildinfo"
 }
 
-unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
+unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:{product-version)"
 
-# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_1.9/dynamic-plugins.default.yaml
+# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_{product-version)/dynamic-plugins.default.yaml
 ----
 
 . Mirror the images in the `ImageSetConfiguration.yaml` file by running the `oc-mirror` command. For example:

modules/extend_orchestrator-in-rhdh/proc-install-rhdh-with-orchestrator-in-a-partially-disconnected-ocp-environment-using-the-helm-chart.adoc

@@ -168,9 +168,9 @@ unpack () {
   cd $DIR; tree -d -L 3 -I "usr|root|buildinfo"
 }
 
-unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
+unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:{product-version)"
 
-# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_1.9/dynamic-plugins.default.yaml
+# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_{product-version)/dynamic-plugins.default.yaml
 ----
 
 .Verification

modules/extend_orchestrator-in-rhdh/proc-install-rhdh-with-orchestrator-in-a-partially-disconnected-ocp-environment-using-the-operator.adoc

@@ -30,7 +30,7 @@ mirror:
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator@_<digest>_
   - name: registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-form-widgets@_<digest>_
-  
+
   operators:
     - catalog: registry.redhat.io/redhat/redhat-operator-index:v<ocp-version>
      # For example: registry.redhat.io/redhat/redhat-operator-index:v{ocp-version}
@@ -66,9 +66,9 @@ unpack () {
   cd $DIR; tree -d -L 3 -I "usr|root|buildinfo"
 }
 
-unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:1.9"
+unpack "registry.access.redhat.com/rhdh/plugin-catalog-index:{product-version)"
 
-# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_1.9/dynamic-plugins.default.yaml
+# you can then find the `dynamic-plugins.default.yaml` under /tmp/registry.access.redhat.com/rhdh/plugin-catalog-index_{product-version)/dynamic-plugins.default.yaml
 ----
 
 . Mirror the images in the `ImageSetConfiguration.yaml` file by running the `oc-mirror` command. For example:

modules/shared/proc-configure-front-end-plugin-wiring.adoc

@@ -58,4 +58,4 @@ plugins:
 After restarting {product-very-short}, confirm that *Simple Example* appears in the sidebar menu. Click *Simple Example* and verify that the plugin page displays correctly. Navigate to a Component entity page and verify that the *ExampleCard* appears in the *Overview* tab.
 
 .Additional resources
-* link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/1.8/html/installing_and_viewing_plugins_in_red_hat_developer_hub/assembly-front-end-plugin-wiring.adoc_rhdh-extensions-plugins[Frontend Plugin Wiring]
+* link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/latest/html/installing_and_viewing_plugins_in_red_hat_developer_hub/assembly-front-end-plugin-wiring.adoc_rhdh-extensions-plugins[Frontend Plugin Wiring]

modules/shared/proc-override-translations.adoc

@@ -56,7 +56,7 @@ $ oc create configmap all-translations \
 As shown in the following examples, we recommend that you use the same mount path for your `allTranslations.json` file and any other override files that you create, for example `/opt/app-root/src/translations`.
 ====
 +
-.. For an Operator-installed {product-very-short} instance, update your `{product-custom-resource-type}` custom resource (CR). For more information about configuring a CR, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/{product-version}/html/configuring_red_hat_developer_hub/provisioning-and-using-your-custom-configuration#using-the-operator-to-run-rhdh-with-your-custom-configuration[Using the {product} Operator to run {product-short} with your custom configuration].
+.. For an Operator-installed {product-very-short} instance, update your `{product-custom-resource-type}` custom resource (CR). For more information about configuring a CR, see link:https://docs.redhat.com/en/documentation/red_hat_developer_hub/latest/html/configuring_red_hat_developer_hub/provisioning-and-using-your-custom-configuration#using-the-operator-to-run-rhdh-with-your-custom-configuration[Using the {product} Operator to run {product-short} with your custom configuration].
 ... In the `spec.application.extraFiles` section, add the translations custom app configuration as shown in the following example:
 +
 .{product-custom-resource-type} custom resource fragment