From 07f846975b8d57c39af24574954423ac11461645 Mon Sep 17 00:00:00 2001
From: James Maes <james@kof22.com>
Date: Fri, 6 Nov 2026 09:49:40 -0600
Subject: [PATCH] build: pin QQQ Core 4.1.0-RC.22 and Collaboration 1.0.0 for
 the first release candidate

Replace the Core RC.21 and Collaboration SNAPSHOT placeholders with the
published coordinates so the first release candidate builds from the registry.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
---
 pom.xml | 10 ++++------
 1 file changed, 4 insertions(+), 6 deletions(-)

diff --git a/pom.xml b/pom.xml
index a9210d3..258a1f6 100644
--- a/pom.xml
+++ b/pom.xml
@@ -22,12 +22,10 @@
       <maven.compiler.source>21</maven.compiler.source>
       <maven.compiler.target>21</maven.compiler.target>
       <jacoco.version>0.8.15</jacoco.version>
-      <!-- Released qqq (Maven Central); one core for the whole module, imported through qqq-bom-pom (see the qqq-snapshot profile). -->
-      <qqq.version>4.1.0-RC.21</qqq.version>
-      <!-- NOTE: collaboration's lifecycle code also needs core after-rollback callbacks (CORE-DEPENDENCY.md); raise this to the core release that has them. -->
-      <!-- Candidate collaboration carrying the attachment lifecycle SPI (feat/record-files-standalone, not yet released).
-           Not in public 0.1.0-RC.6. Qualify with a locally installed 0.1.0-SNAPSHOT; see COLLABORATION-HANDOFF.md. -->
-      <qbit-collaboration.version>0.1.0-SNAPSHOT</qbit-collaboration.version>
+      <!-- QQQ Core 4.1.0-RC.22 from the Gitea registry, imported through qqq-bom-pom. It includes the after-rollback callbacks Collaboration needs. -->
+      <qqq.version>4.1.0-RC.22</qqq.version>
+      <!-- Released Collaboration carrying the attachment lifecycle SPI. -->
+      <qbit-collaboration.version>1.0.0</qbit-collaboration.version>
    </properties>
 
    <parent>
-- 
2.54.0