Update stack-version to 9.0.1

deploy-manage/deploy/self-managed/install-elasticsearch-with-zip-on-windows.md

@@ -40,7 +40,7 @@ On Windows, the {{es}} {{ml}} feature requires the Microsoft Universal C Runtime
 ## Step 1: Download and install the `.zip` package [install-windows]
 
 % link url manually set
-Download the `.zip` archive for {{es}} {{stack-version}} from: [https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{{stack-version}}-windows-x86_64.zip](https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-9.0.0-windows-x86_64.zip)
+Download the `.zip` archive for {{es}} {{stack-version}} from: [https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{{stack-version}}-windows-x86_64.zip](https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-{{stack-version}}-windows-x86_64.zip)
 
 Unzip it with your favorite unzip tool. This will create a folder called `elasticsearch-<version>`, which we will refer to as `%ES_HOME%`. In a terminal window, `cd` to the `%ES_HOME%` directory, for instance:
 

deploy-manage/deploy/self-managed/install-kibana-on-windows.md

@@ -20,7 +20,7 @@ applies_to:
 
 ## Step 1: Download and install the `.zip` package [install-windows]
 
-Download the .zip windows archive for {{kib}} {{stack-version}} from [https://artifacts.elastic.co/downloads/kibana/kibana-{{stack-version}}-windows-x86_64.zip](https://artifacts.elastic.co/downloads/kibana/kibana-9.0.0-windows-x86_64.zip)
+Download the .zip windows archive for {{kib}} {{stack-version}} from [https://artifacts.elastic.co/downloads/kibana/kibana-{{stack-version}}-windows-x86_64.zip](https://artifacts.elastic.co/downloads/kibana/kibana-{{stack-version}}-windows-x86_64.zip)
 
 Unzip it with your favorite unzip tool. This will create a folder called kibana-{{stack-version}}-windows-x86_64, which we will refer to as `$KIBANA_HOME`. In a terminal window, CD to the `$KIBANA_HOME` directory, for instance:
 

deploy-manage/deploy/self-managed/install-kibana-with-debian-package.md

@@ -88,7 +88,7 @@ shasum -a 512 kibana-{{stack-version}}-amd64.deb <1>
 sudo dpkg -i kibana-{{stack-version}}-amd64.deb
 ```
 
-1. 	Compare the SHA produced by shasum with the [published SHA](https://artifacts.elastic.co/downloads/kibana/kibana-9.0.0-amd64.deb.sha512).
+1. 	Compare the SHA produced by shasum with the [published SHA](https://artifacts.elastic.co/downloads/kibana/kibana-{{stack-version}}-amd64.deb.sha512).
 
 % version manually specified in the link above
 

docset.yml

@@ -1,4 +1,4 @@
 project: 'Elastic documentation'
 max_toc_depth: 2
 
 features:
@@ -72,6 +72,10 @@
   - hidden: 404.md
 
 subs:
+  # Do NOT change `stack-version` substitution key.
+  # This may eventually be replaced with a site-wide strategy.
+  # Refer to https://github.com/elastic/docs-builder/issues/737.
+  stack-version: "9.0.1"
   subscriptions:   "https://www.elastic.co/subscriptions"
   ecloud:   "Elastic Cloud"
   ech:   "Elastic Cloud Hosted"
@@ -270,14 +274,11 @@
   fleet-server-issue:   "https://github.com/elastic/fleet-server/issues/"
   fleet-server-pull:   "https://github.com/elastic/fleet-server/pull/"
   kib-pull:   "https://github.com/elastic/kibana/pull/"
-  stack-version: "9.0.0"
   eck_version: "3.0.0"
   eck_release_branch: "3.0"
   eck_helm_minimum_version: "3.2.0"
   eck_resources_list: "Elasticsearch, Kibana, APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash"
   eck_resources_list_short: "APM Server, Beats, Elastic Agent, Elastic Maps Server, and Logstash"
-  apm_server_version: "9.0.0"
-  version: "9.0.0"
   release-date: "2-April-2025"
   heroku: "Elasticsearch Add-on for Heroku"
   obs-ai-assistant: "Elastic AI Assistant for Observability and Search"

explore-analyze/alerts-cases/alerts/alerting-troubleshooting.md

@@ -191,7 +191,7 @@ This approach should be used only temporarily as a last resort to restore functi
 
 ## Limitations [alerting-limitations]
 
-The following limitations and known problems apply to the {{version}} release of the {{kib}} {{alert-features}}:
+The following limitations and known problems apply to the {{stack-version}} release of the {{kib}} {{alert-features}}:
 
 ### Alert visibility [_alert_visibility]
 

explore-analyze/machine-learning/anomaly-detection/ml-limitations.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 # Limitations [ml-limitations]
 
-The following limitations and known problems apply to the {{version}} release of the Elastic {{ml-features}}. The limitations are grouped into four categories:
+The following limitations and known problems apply to the {{stack-version}} release of the Elastic {{ml-features}}. The limitations are grouped into four categories:
 
 * [Platform limitations](#ad-platform-limitations) are related to the platform that hosts the {{ml}} feature of the {{stack}}.
 * [Configuration limitations](#ad-config-limitations) apply to the configuration process of the {{anomaly-jobs}}.

explore-analyze/machine-learning/data-frame-analytics/ml-dfa-limitations.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 # Limitations [ml-dfa-limitations]
 
-The following limitations and known problems apply to the {{version}} release of the Elastic {{dfanalytics}} feature. The limitations are grouped into the following categories:
+The following limitations and known problems apply to the {{stack-version}} release of the Elastic {{dfanalytics}} feature. The limitations are grouped into the following categories:
 
 * [Platform limitations](#dfa-platform-limitations) are related to the platform that hosts the {{ml}} feature of the {{stack}}.
 * [Configuration limitations](#dfa-config-limitations) apply to the configuration process of the {{dfanalytics-jobs}}.

explore-analyze/machine-learning/nlp/ml-nlp-limitations.md

@@ -8,7 +8,7 @@ mapped_pages:
 
 # Limitations [ml-nlp-limitations]
 
-The following limitations and known problems apply to the {{version}} release of the Elastic {{nlp}} trained models feature.
+The following limitations and known problems apply to the {{stack-version}} release of the Elastic {{nlp}} trained models feature.
 
 ## Document size limitations when using `semantic_text` fields [ml-nlp-large-documents-limit-10k-10mb]
 

explore-analyze/query-filter/languages/sql-jdbc.md

@@ -25,7 +25,7 @@ Maven dependency
 <dependency>
   <groupId>org.elasticsearch.plugin</groupId>
   <artifactId>x-pack-sql-jdbc</artifactId>
-  <version>{{version}}</version>
+  <version>{{stack-version}}</version>
 </dependency>
 ```
 
@@ -46,7 +46,7 @@ from [Maven Central Repository](https://search.maven.org/artifact/org.elasticsea
 Your driver must be compatible with your {{es}} version.
 
 ::::{important}
-The driver version cannot be newer than the {{es}} version. For example, {{es}} version 7.10.0 is not compatible with {{version}} drivers.
+The driver version cannot be newer than the {{es}} version. For example, {{es}} version 7.10.0 is not compatible with {{stack-version}} drivers.
 ::::
 
 

explore-analyze/query-filter/languages/sql-odbc-installation.md

@@ -42,7 +42,7 @@ When installing the MSI, the Windows Defender SmartScreen might warn about runni
 Your driver must be compatible with your {{es}} version.
 
 ::::{important}
-The driver version cannot be newer than the {{es}} version. For example, {{es}} version 7.10.0 is not compatible with {{version}} drivers.
+The driver version cannot be newer than the {{es}} version. For example, {{es}} version 7.10.0 is not compatible with {{stack-version}} drivers.
 ::::
 
 
@@ -53,7 +53,7 @@ The driver version cannot be newer than the {{es}} version. For example, {{es}}
 
 ## Download the `.msi` package(s) [download]
 
-Download the `.msi` package for Elasticsearch SQL ODBC Driver {{version}} from: [https://www.elastic.co/downloads/odbc-client](https://www.elastic.co/downloads/odbc-client)
+Download the `.msi` package for Elasticsearch SQL ODBC Driver {{stack-version}} from: [https://www.elastic.co/downloads/odbc-client](https://www.elastic.co/downloads/odbc-client)
 
 There are two versions of the installer available:
 
@@ -82,7 +82,7 @@ Clicking **Next** will present the End User License Agreement. You will need to
 The following screen allows you to customise the installation path for the Elasticsearch ODBC driver files.
 
 ::::{note}
-The default installation path is of the format: **%ProgramFiles%\Elastic\ODBCDriver\\{{version}}**
+The default installation path is of the format: **%ProgramFiles%\Elastic\ODBCDriver\\{{stack-version}}**
 ::::
 
 
@@ -128,19 +128,19 @@ The examples given below apply to installation of the 64 bit MSI package. To ach
 The `.msi` can also be installed via the command line. The simplest installation using the same defaults as the GUI is achieved by first navigating to the download directory, then running:
 
 ```sh subs=true
-msiexec.exe /i esodbc-{{version}}-windows-x86_64.msi /qn
+msiexec.exe /i esodbc-{{stack-version}}-windows-x86_64.msi /qn
 ```
 
 By default, `msiexec.exe` does not wait for the installation process to complete, since it runs in the Windows subsystem. To wait on the process to finish and ensure that `%ERRORLEVEL%` is set accordingly, it is recommended to use `start /wait` to create a process and wait for it to exit:
 
 ```sh subs=true
-start /wait msiexec.exe /i esodbc-{{version}}-windows-x86_64.msi /qn
+start /wait msiexec.exe /i esodbc-{{stack-version}}-windows-x86_64.msi /qn
 ```
 
 As with any MSI installation package, a log file for the installation process can be found within the `%TEMP%` directory, with a randomly generated name adhering to the format `MSI<random>.LOG`. The path to a log file can be supplied using the `/l` command line argument
 
 ```sh subs=true
-start /wait msiexec.exe /i esodbc-{{version}}-windows-x86_64.msi /qn /l install.log
+start /wait msiexec.exe /i esodbc-{{stack-version}}-windows-x86_64.msi /qn /l install.log
 ```
 
 Supported Windows Installer command line arguments can be viewed using:
@@ -156,12 +156,12 @@ msiexec.exe /help
 All settings exposed within the GUI are also available as command line arguments (referred to as *properties* within Windows Installer documentation) that can be passed to `msiexec.exe`:
 
 `INSTALLDIR`
-:   The installation directory. Defaults to _%ProgramFiles%\Elastic\ODBCDriver\\{{version}}_.
+:   The installation directory. Defaults to _%ProgramFiles%\Elastic\ODBCDriver\\{{stack-version}}_.
 
 To pass a value, simply append the property name and value using the format `<PROPERTYNAME>="<VALUE>"` to the installation command. For example, to use a different installation directory to the default one:
 
 ```sh subs=true
-start /wait msiexec.exe /i esodbc-{{version}}-windows-x86_64.msi /qn INSTALLDIR="c:\CustomDirectory"
+start /wait msiexec.exe /i esodbc-{{stack-version}}-windows-x86_64.msi /qn INSTALLDIR="c:\CustomDirectory"
 ```
 
 Consult the [Windows Installer SDK Command-Line Options](https://msdn.microsoft.com/en-us/library/windows/desktop/aa367988(v=vs.85).aspx) for additional rules related to values containing quotation marks.
@@ -191,11 +191,11 @@ Once opened, find the Elasticsearch ODBC Driver installation within the list of
 Uninstallation can also be performed from the command line by navigating to the directory containing the `.msi` package and running:
 
 ```sh subs=true
-start /wait msiexec.exe /x esodbc-{{version}}-windows-x86_64.msi /qn
+start /wait msiexec.exe /x esodbc-{{stack-version}}-windows-x86_64.msi /qn
 ```
 
 Similar to the install process, a path for a log file for the uninstallation process can be passed using the `/l` command line argument
 
 ```sh subs=true
-start /wait msiexec.exe /x esodbc-{{version}}-windows-x86_64.msi /qn /l uninstall.log
+start /wait msiexec.exe /x esodbc-{{stack-version}}-windows-x86_64.msi /qn /l uninstall.log
 ```

explore-analyze/transforms/transform-limitations.md

@@ -9,7 +9,7 @@ mapped_pages:
 
 # Limitations [transform-limitations]
 
-The following limitations and known problems apply to the {{version}} release of the Elastic {{transform}} feature. The limitations are grouped into the following categories:
+The following limitations and known problems apply to the {{stack-version}} release of the Elastic {{transform}} feature. The limitations are grouped into the following categories:
 
 * [Configuration limitations](#transform-config-limitations) apply to the configuration process of the {{transforms}}.
 * [Operational limitations](#transform-operational-limitations) affect the behavior of the {{transforms}} that are running.

explore-analyze/visualize/maps/maps-connect-to-ems.md

@@ -42,7 +42,7 @@ Headers for the Tile Service JSON manifest describing the basemaps available.
 ::::::{tab-item} Curl Example
 ::::{dropdown}
 ```bash subs=true
-curl -I 'https://tiles.maps.elastic.co/v9.0/manifest?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{version}}' \
+curl -I 'https://tiles.maps.elastic.co/v9.0/manifest?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{stack-version}}' \
 -H 'User-Agent: curl/7.81.0' \
 -H 'Accept: */*' \
 -H 'Accept-Encoding: gzip, deflate, br'
@@ -122,7 +122,7 @@ Headers for a vector tile asset in *protobuffer* format from the Tile Service.
 ::::::{tab-item} Curl Example
 ::::{dropdown}
 ```bash subs=true
-$ curl -I 'https://tiles.maps.elastic.co/data/v3/1/1/0.pbf?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{version}}' \
+$ curl -I 'https://tiles.maps.elastic.co/data/v3/1/1/0.pbf?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{stack-version}}' \
 -H 'User-Agent: curl/7.81.0' \
 -H 'Accept: */*' \
 -H 'Accept-Encoding: gzip, deflate, br'
@@ -285,7 +285,7 @@ Headers for the File Service JSON manifest that declares all the datasets availa
 ::::::{tab-item} Curl example
 ::::{dropdown}
 ```bash subs=true
-curl -I 'https://vector.maps.elastic.co/v9.0/manifest?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{version}}' \
+curl -I 'https://vector.maps.elastic.co/v9.0/manifest?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{stack-version}}' \
 -H 'User-Agent: curl/7.81.0' \
 -H 'Accept: */*' \
 -H 'Accept-Encoding: gzip, deflate, br'
@@ -376,7 +376,7 @@ Headers for a sample Dataset from the File Service in TopoJSON format.
 ::::::{tab-item} Curl example
 ::::{dropdown}
 ```bash subs=true
-curl -I 'https://vector.maps.elastic.co/files/world_countries_v7.topo.json?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{version}}' \
+curl -I 'https://vector.maps.elastic.co/files/world_countries_v7.topo.json?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version={{stack-version}}' \
 -H 'User-Agent: curl/7.81.0' \
 -H 'Accept: */*' \
 -H 'Accept-Encoding: gzip, deflate, br'
@@ -485,20 +485,20 @@ If you cannot connect to Elastic Maps Service from the {{kib}} server or browser
 1. Pull the {{hosted-ems}} Docker image.
 
     ```bash subs=true
-    docker pull docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}}
+    docker pull docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}}
     ```
 
 2. Optional: Install [Cosign](https://docs.sigstore.dev/system_config/installation/) for your environment. Then use Cosign to verify the {{es}} image’s signature.
 
     ```sh subs=true
     wget https://artifacts.elastic.co/cosign.pub
-    cosign verify --key cosign.pub docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}}
+    cosign verify --key cosign.pub docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}}
     ```
 
     The `cosign` command prints the check results and the signature payload in JSON format:
 
     ```sh subs=true
-    Verification for docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}} --
+    Verification for docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}} --
     The following checks were performed on each of these signatures:
       - The cosign claims were validated
       - Existence of the claims in the transparency log was verified offline
@@ -509,7 +509,7 @@ If you cannot connect to Elastic Maps Service from the {{kib}} server or browser
 
     ```bash subs=true
     docker run --rm --init --publish 8080:8080 \
-      docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}}
+      docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}}
     ```
 
     Once {{hosted-ems}} is running, follow instructions from the webpage at `localhost:8080` to define a configuration file and optionally download a more detailed basemaps database.
@@ -564,7 +564,7 @@ One way to configure {{hosted-ems}} is to provide `elastic-maps-server.yml` via
 ```yaml subs=true
 services:
   ems-server:
-    image: docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}}
+    image: docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}}
     volumes:
       - ./elastic-maps-server.yml:/usr/src/app/server/config/elastic-maps-server.yml
 ```
@@ -584,7 +584,7 @@ These variables can be set with `docker-compose` like this:
 ```yaml subs=true
 services:
   ems-server:
-    image: docker.elastic.co/elastic-maps-service/elastic-maps-server:{{version}}
+    image: docker.elastic.co/elastic-maps-service/elastic-maps-server:{{stack-version}}
     environment:
       ELASTICSEARCH_HOST: http://elasticsearch.example.org
       ELASTICSEARCH_USERNAME: 'ems'

reference/fleet/running-on-kubernetes-standalone.md

@@ -51,8 +51,8 @@ You can find {{agent}} Docker images [here](https://www.docker.elastic.co/r/elas
 
 Download the manifest file:
 
-```sh
-curl -L -O https://raw.githubusercontent.com/elastic/elastic-agent/v9.0.0/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml
+```sh subs=true
+curl -L -O https://raw.githubusercontent.com/elastic/elastic-agent/v{{stack-version}}/deploy/kubernetes/elastic-agent-standalone-kubernetes.yaml
 ```
 
 ::::{note}

solutions/observability/apm/apm-server-command-reference.md

@@ -174,7 +174,7 @@ Also see [Global flags](#apm-global-flags).
 
 ```sh subs=true
 apm-server export config
-apm-server export template --es.version {{version}} --index myindexname
+apm-server export template --es.version {{stack-version}} --index myindexname
 ```
 
 ## `help` command [apm-help-command]

solutions/observability/apm/apm-server-information-api.md

@@ -51,15 +51,15 @@ curl --verbose -X GET http://127.0.0.1:8200
 
 Example APM Server information request with GET, with a [Secret token](/solutions/observability/apm/secret-token.md):
 
-```sh
+```sh subs=true
 curl -X GET http://127.0.0.1:8200/ \
   -H "Authorization: Bearer secret_token"
 
 {
   "build_date": "2021-12-18T19:59:06Z",
   "build_sha": "24fe620eeff5a19e2133c940c7e5ce1ceddb1445",
   "publish_ready": true,
-  "version": "9.0.0"
+  "version": "{{stack-version}}"
 }
 ```
 

solutions/observability/apm/configure-kafka-output.md

@@ -135,7 +135,7 @@ output.kafka:
         message: "ERR"
 ```
 
-This configuration results in topics named _critical-{{version}}_, _error-{{version}}_, and _logs-{{version}}_.
+This configuration results in topics named _critical-{{stack-version}}_, _error-{{stack-version}}_, and _logs-{{stack-version}}_.
 
 ### `key` [_key]
 

solutions/observability/apm/configure-logstash-output.md

@@ -95,7 +95,7 @@ Every event sent to {{ls}} contains a special field called [`@metadata`](logstas
     ...
     "@metadata": {
       "beat": "apm-server", <1>
-      "version": "{{version}}" <2>
+      "version": "{{stack-version}}" <2>
     }
 }
 ```
@@ -218,7 +218,7 @@ The `proxy_use_local_resolver` option determines if {{ls}} hostnames are resolve
 
 #### `index` [apm-logstash-index]
 
-The index root name to write events to. The default is `apm-server`. For example `"apm"` generates `"[apm-]VERSION-YYYY.MM.DD"` indices (for example, _"apm-{{version}}-2017.04.26"_).
+The index root name to write events to. The default is `apm-server`. For example `"apm"` generates `"[apm-]VERSION-YYYY.MM.DD"` indices (for example, _"apm-{{stack-version}}-2017.04.26"_).
 
 ::::{note}
 This parameter’s value will be assigned to the `metadata.beat` field. It can then be accessed in {{ls}}'s output section as `%{[@metadata][beat]}`.