From 559b738325e599727904bc15cd3c64a08737eb53 Mon Sep 17 00:00:00 2001
From: James Maes <james@kof22.com>
Date: Fri, 6 Nov 2026 08:20:36 -0600
Subject: [PATCH] fix: keep the literal revision tag out of the root POM
 comment

The shared Maven workflow reads the version with grep -m1 on the revision
element, so a comment mentioning the element made it parse prose as the
version and fail every publish run.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index fe1b625..bd44ce2 100644
--- a/pom.xml
+++ b/pom.xml
@@ -1,7 +1,7 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
-   <!-- Reactor root AND parent of every module, so the one <revision> below is the single version source: the release pipeline rewrites only this root property and
+   <!-- Reactor root AND parent of every module, so the one revision property below is the single version source: the release pipeline rewrites only this root property and
         passes no -Drevision, so a module that declared its own revision would stay at the SNAPSHOT. The root keeps the modules' own former parent (qbit-build-parent
         2.0.0), so each module's inherited build configuration is unchanged; each module still keeps its own dependency boundary and can be built on its own
         (mvn -f <module>/pom.xml resolves this parent through ../pom.xml). -->
-- 
2.54.0