From 858d9856b85cfcbc0aae4f2942db0b170a409f91 Mon Sep 17 00:00:00 2001 From: rhdh-bot service account Date: Thu, 14 May 2026 15:21:19 -0300 Subject: [PATCH 1/2] chore: tagRelease.sh: bump to 1.10 in main branch [skip-build] [skip-e2e] Signed-off-by: rhdh-bot service account --- default.env | 2 +- docs/rhdh-local-guide/container-image-guide.md | 14 +++++++------- 2 files changed, 8 insertions(+), 8 deletions(-) diff --git a/default.env b/default.env index cdc8927c..9d1b8828 100644 --- a/default.env +++ b/default.env @@ -13,7 +13,7 @@ BASE_URL=http://localhost:7007 # Default plugin catalog index image # Requires RHDH 1.9+ to be handled. -CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.9 +CATALOG_INDEX_IMAGE=quay.io/rhdh/plugin-catalog-index:1.10 # Path in the install-dynamic-plugins container where the extensions catalog entities should be extracted to, from the catalog index image # Requires RHDH 1.9+ to be handled diff --git a/docs/rhdh-local-guide/container-image-guide.md b/docs/rhdh-local-guide/container-image-guide.md index d9745b25..2365ddd9 100644 --- a/docs/rhdh-local-guide/container-image-guide.md +++ b/docs/rhdh-local-guide/container-image-guide.md @@ -10,7 +10,7 @@ This allows RHDH-local to pull OCI artifacts from registries like registry.redha ## Changing the container image -By default, the [compose.yaml](https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml) points to the latest, stable **community build of RHDH** at [quay.io/rhdh-community/rhdh:1.7](https://quay.io/rhdh-community/rhdh:1.7), which includes both `linux-amd64` and `linux-arm64` images. +By default, the [compose.yaml](https://github.com/redhat-developer/rhdh-local/blob/main/compose.yaml) points to the latest, stable **community build of RHDH** at [quay.io/rhdh-community/rhdh:1.9](https://quay.io/rhdh-community/rhdh:1.9), which includes both `linux-amd64` and `linux-arm64` images. Community builds are [built with Github Actions](https://github.com/redhat-developer/rhdh/blob/main/.github/workflows/next-build-image.yaml#L46-L47) and [docker buildx](https://github.com/redhat-developer/rhdh/blob/main/.github/actions/docker-build/action.yaml), using the same sources as the commercially supported builds. @@ -26,10 +26,10 @@ Looking for the bleeding edge? To use the most recent nightly community build of RHDH_IMAGE=quay.io/rhdh-community/rhdh:next ``` -Or, for builds from a given `release-1.y` branch (for example, 1.8), set the variable as follows. +Or, for builds from a given `release-1.y` branch (for example, 1.10), set the variable as follows. ```sh -RHDH_IMAGE=quay.io/rhdh-community/rhdh:next-1.8 +RHDH_IMAGE=quay.io/rhdh-community/rhdh:next-1.10 ``` ### Using unsupported pre-release CI builds @@ -38,20 +38,20 @@ Continuous Integration (CI) builds on from [quay.io/rhdh/rhdh-hub-rhel9](https:/ NOTE: Only `linux-amd64` builds are currently commercially supported. -To use the most recent nightly CI build of RHDH 1.y (for example, 1.8), set the variable as follows. +To use the most recent nightly CI build of RHDH 1.y (for example, 1.11), set the variable as follows. ```sh -RHDH_IMAGE=quay.io/rhdh/rhdh-hub-rhel9:1.8 +RHDH_IMAGE=quay.io/rhdh/rhdh-hub-rhel9:1.10 ``` ### Using commercially supported official images -To use the [official release of RHDH](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?gs&q=developer%20hub) 1.y (for example, 1.8), which includes only `linux-amd64`, set the variable as follows. +To use the [official release of RHDH](https://catalog.redhat.com/software/containers/rhdh/rhdh-hub-rhel9/645bd4c15c00598369c31aba?gs&q=developer%20hub) 1.y (for example, 1.9), which includes only `linux-amd64`, set the variable as follows. NOTE: Using official builds also [requires authentication with the registry](https://access.redhat.com/articles/RegistryAuthentication). See also the section below `Configuring registry credentials` to make this authentication pervasive. ```sh -RHDH_IMAGE=registry.redhat.io/rhdh/rhdh-hub-rhel9:1.8.3 +RHDH_IMAGE=registry.redhat.io/rhdh/rhdh-hub-rhel9:1.9 ``` #### Using image digests From 38583fcda9f8ad81d0e8bdc1c287496c4d81950b Mon Sep 17 00:00:00 2001 From: Armel Soro Date: Mon, 18 May 2026 10:26:29 +0200 Subject: [PATCH 2/2] set RHDH image to 1.10 This will exist when 1.10 is officially out --- compose.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/compose.yaml b/compose.yaml index 4a715041..c4822c1a 100644 --- a/compose.yaml +++ b/compose.yaml @@ -23,7 +23,7 @@ services: rhdh: container_name: rhdh - image: ${RHDH_IMAGE:-quay.io/rhdh-community/rhdh:1.9} + image: ${RHDH_IMAGE:-quay.io/rhdh-community/rhdh:1.10} env_file: - path: "./default.env" required: true @@ -53,7 +53,7 @@ services: install-dynamic-plugins: container_name: rhdh-plugins-installer - image: ${RHDH_IMAGE:-quay.io/rhdh-community/rhdh:1.9} + image: ${RHDH_IMAGE:-quay.io/rhdh-community/rhdh:1.10} # docker compose volumes are owned by root, so we need to run as root to write to them # the main rhdh container will be able to read from this as files are world readable user: "root"