Sync documentation of main branch

actions-user · actions-user · commit 8ad97a19c34c · 2025-08-20T01:59:56.000Z
diff --git a/_generated-doc/main/config/quarkus-all-config.adoc b/_generated-doc/main/config/quarkus-all-config.adoc
@@ -3176,7 +3176,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -3731,7 +3731,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -10401,7 +10401,7 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |
 
-h|[.configroot-name]##Testing##
+h|[.configroot-name]##Testing configuration##
 h|Type
 h|Default
 
@@ -74662,6 +74662,31 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`+++false+++`
 
+a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-enabled]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-enabled[`quarkus.otel.traces.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.otel.traces.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Enable tracing with OpenTelemetry.
+
+This property is not available in the Open Telemetry SDK. It's Quarkus specific.
+
+Support for OpenTelemetry Tracing will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Tracing will also be disabled.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OTEL_TRACES_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OTEL_TRACES_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`+++true+++`
+
 a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-exporter]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-exporter[`quarkus.otel.traces.exporter`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.otel.traces.exporter+++[]
diff --git a/_generated-doc/main/config/quarkus-container-image-jib.adoc b/_generated-doc/main/config/quarkus-container-image-jib.adoc
@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/main/config/quarkus-container-image-jib_quarkus.jib.adoc b/_generated-doc/main/config/quarkus-container-image-jib_quarkus.jib.adoc
@@ -15,7 +15,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21-runtime:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17-runtime:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/main/config/quarkus-container-image-openshift.adoc b/_generated-doc/main/config/quarkus-container-image-openshift.adoc
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/main/config/quarkus-container-image-openshift_quarkus.openshift.adoc b/_generated-doc/main/config/quarkus-container-image-openshift_quarkus.openshift.adoc
@@ -36,7 +36,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.21` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.21` is used as the default.
+The base image to be used when a container image is being produced for the jar build. The value of this property is used to create an ImageStream for the builder image used in the Openshift build. When it references images already available in the internal Openshift registry, the corresponding streams are used instead. When the application is built against Java 21 or higher, `registry.access.redhat.com/ubi9/openjdk-21:1.23` is used as the default. Otherwise `registry.access.redhat.com/ubi9/openjdk-17:1.23` is used as the default.
 
 
 ifdef::add-copy-button-to-env-var[]
diff --git a/_generated-doc/main/config/quarkus-opentelemetry.adoc b/_generated-doc/main/config/quarkus-opentelemetry.adoc
@@ -55,6 +55,31 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`+++false+++`
 
+a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-enabled]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-enabled[`quarkus.otel.traces.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.otel.traces.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Enable tracing with OpenTelemetry.
+
+This property is not available in the Open Telemetry SDK. It's Quarkus specific.
+
+Support for OpenTelemetry Tracing will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Tracing will also be disabled.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OTEL_TRACES_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OTEL_TRACES_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`+++true+++`
+
 a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-exporter]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-exporter[`quarkus.otel.traces.exporter`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.otel.traces.exporter+++[]
diff --git a/_generated-doc/main/config/quarkus-opentelemetry_quarkus.otel.adoc b/_generated-doc/main/config/quarkus-opentelemetry_quarkus.otel.adoc
@@ -55,6 +55,31 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`+++false+++`
 
+a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-enabled]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-enabled[`quarkus.otel.traces.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.otel.traces.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+Enable tracing with OpenTelemetry.
+
+This property is not available in the Open Telemetry SDK. It's Quarkus specific.
+
+Support for OpenTelemetry Tracing will be enabled if this value is true. The OpenTelemetry SDK ( `io.quarkus.opentelemetry.runtime.config.build.OTelBuildConfig++#++enabled()` ) is enabled by default and if disabled, OpenTelemetry Tracing will also be disabled.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OTEL_TRACES_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OTEL_TRACES_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`+++true+++`
+
 a|icon:lock[title=Fixed at build time] [[quarkus-opentelemetry_quarkus-otel-traces-exporter]] [.property-path]##link:#quarkus-opentelemetry_quarkus-otel-traces-exporter[`quarkus.otel.traces.exporter`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.otel.traces.exporter+++[]
diff --git a/_generated-doc/main/infra/quarkus-maven-plugin-goals.adoc b/_generated-doc/main/infra/quarkus-maven-plugin-goals.adoc
@@ -1457,6 +1457,15 @@ a| [[quarkus-maven-plugin-goal-dev-quarkus.warnIfBuildGoalMissing]] quarkus.warn
 |`boolean`
 |
 
+a| [[quarkus-maven-plugin-goal-dev-watchedFiles]] watchedFiles
+
+[.description]
+--
+Optional list of files to watch for changes that trigger a hot reload in dev mode. This is useful for extensions developers that can set this property to their extension's artifacts in their local repository.
+--
+|`List`
+|
+
 a| [[quarkus-maven-plugin-goal-dev-workingDir]] workingDir
 |`File`
 |
@@ -2452,7 +2461,7 @@ a| [[quarkus-maven-plugin-goal-list-extensions-format]] format
 
 [.description]
 --
-Select the output format among 'id' (display the artifactId only), 'concise' (display name and artifactId) and 'full' (concise format and version related columns).
+Select the output format among 'id' (display the artifactId only), 'concise' (display name and artifactId), 'origins' (display extension catalog IDs providing extension information), 'support-scope' (support scope associated with each extension, if any) and 'full' (concise format and version related columns).
 --
 |`String`
 |`concise`
@@ -3262,6 +3271,15 @@ a| [[quarkus-maven-plugin-goal-remote-dev-quarkus.warnIfBuildGoalMissing]] quark
 |`boolean`
 |
 
+a| [[quarkus-maven-plugin-goal-remote-dev-watchedFiles]] watchedFiles
+
+[.description]
+--
+Optional list of files to watch for changes that trigger a hot reload in dev mode. This is useful for extensions developers that can set this property to their extension's artifacts in their local repository.
+--
+|`List`
+|
+
 a| [[quarkus-maven-plugin-goal-remote-dev-workingDir]] workingDir
 |`File`
 |
@@ -3788,6 +3806,15 @@ a| [[quarkus-maven-plugin-goal-test-quarkus.warnIfBuildGoalMissing]] quarkus.war
 |`boolean`
 |
 
+a| [[quarkus-maven-plugin-goal-test-watchedFiles]] watchedFiles
+
+[.description]
+--
+Optional list of files to watch for changes that trigger a hot reload in dev mode. This is useful for extensions developers that can set this property to their extension's artifacts in their local repository.
+--
+|`List`
+|
+
 a| [[quarkus-maven-plugin-goal-test-workingDir]] workingDir
 |`File`
 |
diff --git a/_versions/main/guides/_attributes.adoc b/_versions/main/guides/_attributes.adoc
@@ -21,7 +21,7 @@
 :keycloak-docker-image: quay.io/keycloak/keycloak:26.3.0
 :jandex-version: 3.4.0
 :jandex-gradle-plugin-version: 1.0.0
-:kotlin-version: 2.2.0
+:kotlin-version: 2.2.10
 :grpc-version: 1.69.1
 :protoc-version: 3.25.5
 :gcf-invoker-version: 1.4.1
diff --git a/_versions/main/guides/building-native-image.adoc b/_versions/main/guides/building-native-image.adoc
@@ -293,9 +293,9 @@ capabilities of `@NativeImageTest`. More information about `@QuarkusIntegrationT
 === Profiles
 By default, integration tests both *build* and *run* the native executable using the `prod` profile.
 
-You can override the profile the executable *runs* with during the test using the `quarkus.test.native-image-profile` property.
+You can override the profile the executable *runs* with during the test using the `quarkus.test.integration-test-profile` property.
 Either by adding it to `application.properties` or by appending it to the command line:
-`./mvnw verify -Dnative -Dquarkus.test.native-image-profile=test`.
+`./mvnw verify -Dnative -Dquarkus.test.integration-test-profile=test`.
 Your `%test.` prefixed properties will be used at the test runtime.
 
 
@@ -564,7 +564,7 @@ The project generation has also provided a `Dockerfile.native` in the `src/main/
 
 [source,dockerfile]
 ----
-FROM registry.access.redhat.com/ubi9/ubi-minimal:9.5
+FROM registry.access.redhat.com/ubi9/ubi-minimal:9.6
 WORKDIR /work/
 RUN chown 1001 /work \
     && chmod "g+rwX" /work \
diff --git a/_versions/main/guides/cli-tooling.adoc b/_versions/main/guides/cli-tooling.adoc
@@ -431,6 +431,7 @@ The format of the result can be controlled with one of four options:
 - `--concise` Display the name (artifactId) and description
 - `--full`    Display concise format and version/status-related columns.
 - `--origins` Display concise information along with the Quarkus platform release origin of the extension.
+- `--support-scope` Display support scope associated with each extension (if any) for an offering configured in the registry client configuration.
 
 The behavior of `quarkus ext ls` will vary depending on context.
 
@@ -465,6 +466,21 @@ Elytron Security JDBC                              quarkus-elytron-security-jdbc
 Agroal - Database connection pool                  quarkus-agroal
 ----
 
+==== Listing extensions for a specific offering
+
+NOTE: This option was introduced in 3.26.0 and will be evolving in the upcoming releases.
+
+As described in link:{quarkus-home-url}/guides/extension-registry-user#limiting-extension-catalog-to-an-offering[the registry client documentation], an extension catalog could be limited to a specific extension offering delivered and supported by a dedicated team or an organization.
+
+When an offering is configured for a registry in `.quarkus/config.yaml`, `ext list --support-scope` can be used to display support scope associated with extensions from the selected offering. For example,
+
+[source,shell]
+----
+quarkus ext list --support-scope
+✬ ArtifactId                                         Extension Name                                     Version                   Support scope
+✬ acme-quarkus-magic                                 Acme Quarkus Magic                                 1.6.16                    tech-preview
+----
+
 ==== Adding extensions
 
 The Quarkus CLI can add one or more extensions to your project with the `add`
diff --git a/_versions/main/guides/extension-metadata.adoc b/_versions/main/guides/extension-metadata.adoc
@@ -18,7 +18,7 @@ IMPORTANT: Two of the metadata files have the same name but different extensions
 
 Every **runtime** extension artifact **must** include this file. This file is used by Quarkus dev tools when displaying information about an extension, creating a new project or adding extensions to an existing project, etc. This file isn't used at application build or bootstrap times.
 The basic and required metadata included in this file can be generated by the Quarkus Maven and Gradle plugins when the extension artifact is built. However, typically, extension authors will want to provide more information about the extension to the Quarkus dev tools and users. The extra information could be provided
-in a template `META-INF/quarkus-extension.yaml` found in the extension runtime module's resources directory, e.g. `src/main/resources/META-INF/quarkus-extension.yaml`. Here is an example of such a template for the `quarkus-resteasy-reactive` extension:
+in a template `META-INF/quarkus-extension.yaml` found in the extension runtime module's resources directory, e.g. `src/main/resources/META-INF/quarkus-extension.yaml`. Here is an example of such a template for the `quarkus-rest` extension:
 
 [source,yaml,subs=attributes+]
 ----
@@ -116,6 +116,27 @@ sponsor: A Sponsoring Organisation <8>
 <7> The source code repository of this extension. Optional, and will often be set automatically by using the `<scm>` information in the pom. In GitHub Actions builds, it will be inferred from the CI environment. For other GitHub repositories, it can be controlled by setting a `GITHUB_REPOSITORY` environment variable.
 <8> The sponsor(s) of this extension. Optional, and will sometimes be determined automatically from commit history.
 
+=== Extension offerings
+
+NOTE: This bit of metadata was introduced in Quarkus 3.26.0 and it will be evolving in the upcoming versions.
+
+An offering is a set of extensions that are delivered and supported by a dedicated team or an organization under certain conditions.
+An extension may be associated with one or more offerings by adding `<offering-id>-support` field to its metadata, specifying support scope as its value. For example, here is a relevant snippet of metadata illustrating how it could look like:
+
+[source,yaml,subs=attributes+]
+----
+name: "Acme Quarkus Magic"
+artifact: "com.acme.quarkus:acme-quarkus-magic:999-SNAPSHOT"
+metadata:
+  acme-cloud-support: [ "supported" ], <1>
+  team-x: [ "tech-preview" ] <2>
+----
+<1> Associates `acme-quarkus-magic` with `acme-cloud` offering with support scope `supported`;
+<2> Associates `acme-quarkus-magic` with `team-x` offering with support scope `tech-preview`.
+
+The meaning of support scopes, such as `supported` and `tech-preview`, would be defined in the offering documentation by the corresponding team or organization.
+
+Offerings and support scopes may be used by Quarkus dev tools, such as Quarkus CLI and code.quarkus, to display and/or filter extensions by the relevant support-related information.
 
 [[quarkus-extension-properties]]
 == META-INF/quarkus-extension.properties
diff --git a/_versions/main/guides/extension-registry-user.adoc b/_versions/main/guides/extension-registry-user.adoc
diff --git a/_versions/main/guides/logging.adoc b/_versions/main/guides/logging.adoc
diff --git a/_versions/main/guides/quarkus-runtime-base-image.adoc b/_versions/main/guides/quarkus-runtime-base-image.adoc
diff --git a/_versions/main/guides/security-oidc-auth0-tutorial.adoc b/_versions/main/guides/security-oidc-auth0-tutorial.adoc
