fix(ci): flip <graphcompose.version> in examples/benchmarks POMs

The new examples-generation CI job introduced in 6e436a8 went red
on its first run with:

    Could not find artifact io.github.demchaav:graphcompose:jar:1.6.0-beta.1
    in central (https://repo.maven.apache.org/maven2)

Root cause: cut-release.ps1's Update-PomVersion flipped only the
first <version> tag in each POM (the project's own version),
leaving the <graphcompose.version> *property* in examples/pom.xml
and benchmarks/pom.xml at the in-flight 1.6.0-beta.1 value. That
property is what the dependency declaration resolves through, so
on a fresh CI agent without a populated local m2 the build couldn't
find the artifact.

Fix forward, in three parts:

1. Subordinate POMs (examples/, benchmarks/) — flip the property
   from 1.6.0-beta.1 to 1.6.0 manually. v1.6.0 jar is already on
   JitPack, so once the property points there, dependency resolution
   succeeds against the JitPack repo declared in the parent.

2. cut-release.ps1 — Update-PomVersion now flips both the first
   <version> tag AND a <graphcompose.version> property if present,
   in the same call. Next release won't need a manual hotfix.

3. docs/release-process.md — capture the v1.6.0 lesson alongside
   the v1.5.0 / v1.6.0-prep ones so a future agent reading the
   runbook understands why the script grew this second regex.

Author: DemchaAV

benchmarks/pom.xml

@@ -16,7 +16,7 @@
     </description>
 
     <properties>
-        <graphcompose.version>1.6.0-beta.1</graphcompose.version>
+        <graphcompose.version>1.6.0</graphcompose.version>
         <maven.compiler.release>21</maven.compiler.release>
 
         <junit.bom.version>5.12.2</junit.bom.version>

docs/release-process.md

@@ -134,6 +134,7 @@ Each learning maps to a check above.
 - **v1.5.0** — `Fixed column 0 width 90 is smaller than required natural width 92.44` only surfaced on `exec:java`, not `mvn test`. *Mitigation*: section B mandates a full `GenerateAllExamples` regen before every release.
 - **v1.5.0** — 8 zero-byte junk files (`examples/p,`, `{,`, `[Help`, etc.) crept into the working tree from accidental shell-output expansions. *Mitigation*: section A hard-gates on `git status --short` cleanliness, not just on the script's pre-flight.
 - **v1.6.0 prep** — slimming the README to a marketing landing renamed the canonical `DocumentSession document = …` example variable to `doc`, which silently broke `DocumentationCoverageTest.readmeShouldUseCanonicalDslAndAvoidLegacyApis` because the test asserts the literal string `document.pageFlow(` is present. *Mitigation*: any rewrite of the README "Hello world" snippet must keep `DocumentSession document` as the variable name and `document.pageFlow(`, `document.buildPdf()`, `GraphCompose.document(` as the literal canonical fingerprints the guard scans for. Renaming the variable is a guard-test break, not a stylistic preference.
+- **v1.6.0 post-release** — the `examples-generation` CI job introduced after v1.6.0 went red on the first run because `examples/pom.xml` and `benchmarks/pom.xml` declare a `<graphcompose.version>` property used by their `graphcompose` dependency, and `cut-release.ps1` was only flipping the project's own `<version>` tag (the first `<version>` in each file). The subordinate POMs kept `<graphcompose.version>1.6.0-beta.1</graphcompose.version>` after the release commit; CI couldn't resolve a `1.6.0-beta.1` artifact (it never existed on any registry), so `mvnw -f examples/pom.xml clean compile` failed at dependency resolution. *Mitigation*: `Update-PomVersion` in `cut-release.ps1` now flips both the first `<version>` tag *and* a `<graphcompose.version>...</graphcompose.version>` property if present, in the same call. Future agents need not touch this — running the script handles both.
 
 ---
 

examples/pom.xml

@@ -11,7 +11,7 @@
     <description>Runnable file-render examples for GraphCompose templates.</description>
 
     <properties>
-        <graphcompose.version>1.6.0-beta.1</graphcompose.version>
+        <graphcompose.version>1.6.0</graphcompose.version>
         <logback.version>1.5.18</logback.version>
         <maven.compiler.release>21</maven.compiler.release>
 

scripts/cut-release.ps1

@@ -108,21 +108,45 @@ function Update-PomVersion($pomPath, $newVersion) {
         return
     }
     $content = Get-Content $pomPath -Raw
-    # Match the FIRST <version> tag in the file — that's the project's
-    # own version, before <parent> or any dependency entries.
-    $regex = [regex]'<version>[\w\.\-]+</version>'
-    $newLine = "<version>$newVersion</version>"
-    $newContent = $regex.Replace($content, $newLine, 1)
-    if ($content -eq $newContent) {
+    $changed = $false
+
+    # 1. Project's own <version> tag (the FIRST <version> in the file,
+    #    before <parent> or any dependency entries).
+    $projectRegex = [regex]'<version>[\w\.\-]+</version>'
+    $projectNew = "<version>$newVersion</version>"
+    $afterProject = $projectRegex.Replace($content, $projectNew, 1)
+    if ($content -ne $afterProject) {
+        $content = $afterProject
+        $changed = $true
+        Note "bumped <version>: $pomPath -> $projectNew"
+    }
+
+    # 2. <graphcompose.version> property (if present). Subordinate POMs
+    #    (examples/, benchmarks/) declare this property and depend on
+    #    "io.github.demchaav:graphcompose:${graphcompose.version}". The
+    #    property must track the project version so the published tag
+    #    actually resolves on a fresh CI agent without a populated
+    #    local m2. Bug surfaced in v1.6.0 release CI: the property
+    #    stayed at 1.6.0-beta.1 while the project version flipped to
+    #    1.6.0 and CI failed at "Could not find artifact ...:1.6.0-beta.1".
+    $propertyRegex = [regex]'<graphcompose\.version>[\w\.\-]+</graphcompose\.version>'
+    $propertyNew = "<graphcompose.version>$newVersion</graphcompose.version>"
+    $afterProperty = $propertyRegex.Replace($content, $propertyNew, 1)
+    if ($content -ne $afterProperty) {
+        $content = $afterProperty
+        $changed = $true
+        Note "bumped <graphcompose.version>: $pomPath -> $propertyNew"
+    }
+
+    if (-not $changed) {
         Note "no change: $pomPath (version already $newVersion?)"
         return
     }
+
     if ($DryRun) {
-        Write-Host "    [DRY RUN] Bump $pomPath -> $newLine" -ForegroundColor Yellow
+        Write-Host "    [DRY RUN] Bump $pomPath -> $newVersion" -ForegroundColor Yellow
     } else {
-        # Write without trailing newline change; preserve original ending.
-        [System.IO.File]::WriteAllText($pomPath, $newContent)
-        Note "bumped: $pomPath -> $newLine"
+        [System.IO.File]::WriteAllText($pomPath, $content)
     }
 }