Use latest version of Asciidoctor plugin, adjust user guide documenta…

…tion

build.gradle.kts

@@ -4,7 +4,7 @@ plugins {
     kotlin("jvm") apply false
     id("com.gradle.plugin-publish") version "1.2.1" apply false
     id("org.jetbrains.dokka")
-    id("org.asciidoctor.jvm.convert") version "3.2.0"
+    id("org.asciidoctor.jvm.convert") version "3.3.2"
 }
 
 

docs/configure-helm.adoc

@@ -96,7 +96,7 @@ The cache home, as indicated by `xdgCacheHome`, defaults to a directory under th
 in a multi-module build, all Helm projects will share the same cache by default. This speeds up builds, but may lead
 to problems in certain situations, for example if two projects register a different chart repository under the same
 name.
-+
+
 If necessary, you can always set the cache home to a project-local directory, for example:
 
 [source,groovy,role="primary"]
@@ -136,7 +136,7 @@ The following example shows how the download can be configured in the build scri
 helm {
     downloadClient {
         enabled = true
-        version = '3.4.1'
+        version = '3.12.3'
     }
 }
 ----
@@ -147,7 +147,7 @@ helm {
 helm {
     downloadClient {
         enabled.set(true)
-        version.set("3.4.1")
+        version.set("3.12.3")
     }
 }
 ----
@@ -159,7 +159,7 @@ The following example shows how the download can be configured using the gradle.
 .gradle.properties
 ----
 helm.client.download.enabled=true
-helm.client.download.version=3.4.1
+helm.client.download.version=3.12.3
 ----
 
 === Using with Multi-Project Builds
@@ -189,7 +189,7 @@ The following properties control the download of the Helm client:
 | `version`
 | `helm.client.download.version`
 | The version of the Helm client to be downloaded.
-| The latest version of Helm available at the time the plugin is published (currently `3.4.1`)
+| The latest version of Helm available at the time the plugin is published (currently `3.12.3`)
 
 |
 | `helm.client.download.baseUrl`

docs/managing-releases.adoc

@@ -432,7 +432,7 @@ helm {
 }
 ----
 
-INFO: If you don't create your own release targets, the plugin will create a release target named `default` that
+NOTE: If you don't create your own release targets, the plugin will create a release target named `default` that
 uses all the default properties. As soon as you create other release targets, the `default` target will back away.
 
 Values (and related properties) can be added to a release target as well, and they will be used for _every_ release
@@ -805,7 +805,7 @@ command line to further narrow down the set of releases per-build.
 ./gradlew helmInstall -Phelm.release.target=local -Phelm.release.tags=application
 ----
 
-INFO: If both `helm.release.tags` and the active release target contain a select expression for tags, they will be
+NOTE: If both `helm.release.tags` and the active release target contain a select expression for tags, they will be
 both combined using "and". This means that a release will only be installed if it matches _both_ the `helm.release.tags`
 expression and the `selectTags` expression of the release target.
 

docs/prerequisites.adoc

@@ -16,5 +16,5 @@ supported by Helm 3, and also by the plugin. (The main difference between `v1` a
 chart dependencies in a file called `requirements.yaml`, whereas in `v2` the dependencies are declared
 directly in the `Chart.yaml` file.)
 +
-INFO: Delegating to the Helm CLI decouples the plugin release cycle from the Helm release cycle, but it also
+NOTE: Delegating to the Helm CLI decouples the plugin release cycle from the Helm release cycle, but it also
 means that some features offered by the plugin may not be available in the CLI and vice versa.