From b2a5c3265910a141c21f7bfbbd6a9c4e89d42400 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Brian=20Sch=C3=A4ffner?= <burnify.design@gmail.com>
Date: Wed, 7 Oct 2026 14:24:42 +0200
Subject: [PATCH] chore: release runtime 1.2.5

---
 CHANGELOG.md                |  7 +++++++
 docs/releases/1.2.5.md      | 24 ++++++++++++++++++++++++
 src/Console/Application.php |  2 +-
 3 files changed, 32 insertions(+), 1 deletion(-)
 create mode 100644 docs/releases/1.2.5.md

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5488a55..f7aa67f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,8 +2,15 @@
 
 ## Unreleased
 
+No changes yet.
+
+## 1.2.5 — 2026-10-07
+
 - Generate native `wp-config.php` directly in the WordPress core parent (`public/` for a `public/wp/` layout), eliminating the default root configuration and forwarding loader. WP-CLI, section editing, setup drift and production diagnostics follow the same target.
 - Recover literal salts from previous managed native root configurations without executing PHP; retain the root file for rollback. Customized sections, dynamic salt providers, location-dependent salt code and root symlinks require explicit migration. Literal salt edits, legacy profile layouts and alternate configuration targets remain supported.
+- Report the current release version in the standalone CLI.
+
+See the [1.2.5 upgrade notes](docs/releases/1.2.5.md).
 
 ## 1.2.4 — 2026-10-05
 
diff --git a/docs/releases/1.2.5.md b/docs/releases/1.2.5.md
new file mode 100644
index 0000000..7485a7d
--- /dev/null
+++ b/docs/releases/1.2.5.md
@@ -0,0 +1,24 @@
+# Runtime 1.2.5
+
+Update `sympress/runtime` with Composer, review the lockfile and regenerate the
+managed configuration with `vendor/bin/runtime --no-interaction`.
+
+For a `public/wp/` core layout, the main configuration now lives directly in
+`public/wp-config.php`. WordPress loads it natively from the core's parent;
+the root configuration and public forwarding loader are no longer required.
+WP-CLI, section editing, setup drift and production diagnostics use the same
+configuration target. Explicit alternate targets and compatibility profiles
+remain supported.
+
+Migration recovers literal authentication keys and salts from an existing managed
+native root configuration without executing it. The previous root file remains
+available for rollback. After verifying WordPress bootstrap and the preserved
+salts, archive that file outside the public website before removing it from the
+project root.
+
+Customized sections, dynamic salt providers, location-dependent salt code and
+root symlinks require explicit migration. These cases fail before generated
+configuration is changed. Literal edits to the managed salt section remain
+supported. See the [compatibility migration guide](../compatibility.md).
+
+The standalone CLI reports version 1.2.5.
diff --git a/src/Console/Application.php b/src/Console/Application.php
index 6ea3cac..c73c11b 100644
--- a/src/Console/Application.php
+++ b/src/Console/Application.php
@@ -31,7 +31,7 @@ public static function main(array $arguments, string $root, string $vendor, ?arr
         $installed = is_file($installedFile) ? json_decode((string) file_get_contents($installedFile), true, 512, JSON_THROW_ON_ERROR) : [];
         $dev = !is_array($installed) || ($installed['dev'] ?? true) !== false;
         $context = $data === null ? new RunContext($root, $vendor, $bin, dev: $dev, manifest: $manifestFile) : RunContext::fromArray($data);
-        $application = new ConsoleApplication('SymPress Runtime', '1.1.1');
+        $application = new ConsoleApplication('SymPress Runtime', '1.2.5');
         $application->setAutoExit(false);
         foreach (['run', ...Registry::RESERVED] as $operation) {
             $application->addCommand(new RuntimeCommand($context, $operation));