build(release): prepare 0.1.0 on published core 4.1.0-RC.22 and qbit-redis 0.1.0-RC.1

Replace the in-flight snapshot coordinates that the shared-session work was built against (qqq-bom-pom 4.1.0-collab-33464d37e-SNAPSHOT, qbit-redis 0.1.0-redis-7fe5492-SNAPSHOT) with published coordinates exposed as overridable properties: qqq.version=4.1.0-RC.22, the first release-line core carrying QSessionStoreRegistry.getInstance(QInstance) and clearIfSame, and qbit-redis.version=0.1.0-RC.1, whose public api is a strict superset of the 7fe5492 snapshot. The revision stays 0.1.0-SNAPSHOT: the shared ci-workflows Maven workflow assigns 0.1.0-RC.N from release/0.1 and 0.1.0 from the v0.1.0 tag, so no version is hand-edited here. CHANGELOG records the 0.1.0 contents; README gains a compatibility matrix and the release/publication procedure for this repository. Verification (Maven 3.9.11, Temurin 21, Docker 29.9.2 for Testcontainers): mvn verify with the same sources installed locally under local-labeled versions (core release/4.1 tip f1cdf31e9 as 4.1.0-local.f1cdf31e9, qbit-redis tag v0.1.0-RC.1 as 0.1.0-local.6b0814d, because the Gitea registry needs an authenticated read from this host): 67 unit tests, 29 integration tests (RedisSessionStoreProviderIT, SharedRedisSessionStoreProviderIT, TableBasedSessionStoreProviderIT) with zero failures/errors/skips, zero Checkstyle violations, JaCoCo coverage gates met. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>
fix: upgrade session-store test assertions to patched AssertJ
2026-11-06 08:53:30 -06:00 · 2026-11-06 08:48:25 -06:00 · 2026-11-06 08:48:15 -06:00 · 2026-11-05 23:18:05 +00:00 · 2026-11-05 16:27:03 -06:00 · 2026-11-05 22:08:23 +00:00
6 changed files with 83 additions and 15 deletions
@@ -1,16 +1,14 @@
 version: 2.1
 setup: true
 orbs:
-  qqq-orb: kingsrook/qqq-orb@0.7.18
+  qqq-orb: kingsrook/qqq-orb@0.8
 workflows:
  setup:
    jobs:
    - qqq-orb/generate_pipeline:
-        orb_version: 0.7.18
+        orb_version: '0.8'
        filters:
          branches:
            ignore: automation/qbit-rc-pending
          tags:
-            only:
-            - /^v\d+\.\d+\.\d+$/
-            - /publish.*/
+            only: /^v\d+\.\d+\.\d+$/
@@ -0,0 +1,7 @@
+name: build
+on:
+  push:
+jobs:
+  maven:
+    uses: self:KofTwentyTwo/ci-workflows/.gitea/workflows/maven.yaml@main
+    secrets: inherit
@@ -1,5 +1,5 @@
 profile: qbit
-orb_version: 0.7.18
+orb_version: '0.8'
 default_branch: develop
 java_version: '21'
 browsers: true
@@ -10,7 +10,6 @@ release_tag_policy: stable
 test_branch_policy: non-release
 publish:
  snapshot: true
-  feature: true
  release_candidate: true
  release: true
  asciidoc: false
@@ -5,7 +5,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

-## [Unreleased] - 0.1.0-SNAPSHOT
+## [Unreleased] - 0.1.0
+
+First published release. Version numbers are assigned by the shared Gitea
+Maven workflow from the branch or tag that publishes (see README "Releasing");
+the `revision` property on `develop` stays `0.1.0-SNAPSHOT` until the release
+merges back.

 ### Added
 - In-memory session store provider with LRU eviction
@@ -15,3 +20,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Sliding expiration (configurable per-provider)
 - Scheduled cleanup process for expired sessions
 - QBit producer for declarative configuration
+- `SHARED_REDIS` provider: application-scoped shared sessions on the pool owned
+  by the optional `qbit-redis` QBit, with explicit deployment/application/
+  authentication-domain namespacing, bounded payloads, atomic GETEX touch, and a
+  runtime service that releases registrations on stop and rebuilds them on
+  restart (`docs/SESSION-REGISTRATION.md`)
+- Explicit `QInstance` overloads on `QSessionStoreQBitContext` and
+  application-scoped registration through
+  `QSessionStoreRegistry.getInstance(qInstance)`; two applications in one JVM
+  no longer see each other's sessions
+- Health check reports the target application selected by `HealthCheckInput`
+
+### Changed
+- Depends on published QQQ core `4.1.0-RC.22` (the first release-line core with
+  `QSessionStoreRegistry.getInstance(QInstance)`) and `qbit-redis 0.1.0-RC.1`;
+  the snapshot coordinates used while the shared-session work was in flight
+  (`4.1.0-collab-33464d37e-SNAPSHOT`, `0.1.0-redis-7fe5492-SNAPSHOT`) are gone
+- Jedis 7.2.0, Testcontainers 2.0.3, AssertJ 3.27.7 (GHSA-rqfh-9r24-8c9r)
+- Hosts that register a provider with core outside a request context must use
+  the explicit `QSessionStoreRegistry.getInstance(qInstance)` overload
@@ -8,7 +8,21 @@ Every QQQ request authenticates and builds a `QSession` containing security keys

 ## Project Status

-**0.1.0-SNAPSHOT** -- under active development. API may change before 1.0.
+**0.1.0** is the first published release line (release candidates publish as
+`0.1.0-RC.N`). API may change before 1.0. See [CHANGELOG.md](CHANGELOG.md).
+
+## Compatibility
+
+| qbit-session-store | QQQ core (`qqq-bom-pom`) | qbit-redis (optional, `SHARED_REDIS` only) |
+|--------------------|--------------------------|--------------------------------------------|
+| 0.1.0 line         | 4.1.0-RC.22 or later 4.1 | 0.1.0-RC.1 or later 0.1                    |
+
+The `SHARED_REDIS` provider and application-scoped registration call
+`QSessionStoreRegistry.getInstance(QInstance)` and `clearIfSame`, which core
+added after 4.1.0-RC.21; this QBit does not compile against RC.21 or earlier.
+Artifacts publish to the Gitea Maven registry
+(`https://git.kof22.com/api/packages/QRun-IO/maven`), which requires an
+authenticated read.

 ## Features

@@ -35,7 +49,7 @@ Add the dependency to your project:
 <dependency>
   <groupId>com.kingsrook.qbits</groupId>
   <artifactId>qbit-session-store</artifactId>
-   <version>0.1.0-SNAPSHOT</version>
+   <version>0.1.0</version>
 </dependency>
 ```

@@ -227,6 +241,26 @@ provider.remove(sessionUuid);

 See [CONTRIBUTING.md](CONTRIBUTING.md) for guidelines.

+## Releasing
+
+Versions are computed by the shared `KofTwentyTwo/ci-workflows` Maven workflow
+(`.gitea/workflows/build.yaml`) from what is pushed; the `revision` property on
+`develop` stays `0.1.0-SNAPSHOT` and is never hand-edited for a release.
+
+| Push                       | Published version        | Side effects                                                  |
+|----------------------------|--------------------------|---------------------------------------------------------------|
+| `develop`                  | `0.1.0-SNAPSHOT`         | none                                                          |
+| branch `release/0.1`       | `0.1.0-RC.1`, `RC.2`, .. | commits "Bump version to X [skip ci]" to the branch, tags `vX` |
+| tag `v0.1.0`               | `0.1.0`                  | pushes the version bump to `main`                             |
+| tag `publish-<name>`       | `0.1.0-<feature>-<sha>-SNAPSHOT` | none                                                  |
+
+To cut the first release: merge this release preparation into `develop`, create
+`release/0.1` from `develop` and push it (publishes `0.1.0-RC.1`), qualify the
+candidate, then tag the bumped `release/0.1` head `v0.1.0` and push the tag
+(publishes `0.1.0`). Merge `release/0.1` back into `develop`; the workflow then
+advances `develop` to `0.2.0-SNAPSHOT`. Record the date in `CHANGELOG.md` when
+tagging. GitHub is a read-only shadow; never push there.
+
 ## License

 Apache-2.0 - See [LICENSE](LICENSE)
@@ -22,7 +22,13 @@
      <maven.compiler.source>21</maven.compiler.source>
      <maven.compiler.target>21</maven.compiler.target>
      <jedis.version>7.2.0</jedis.version>
-      <qqq.snapshot.version>4.1.0-collab-33464d37e-SNAPSHOT</qqq.snapshot.version>
+      <!-- Published QQQ 4.1 core. 4.1.0-RC.22 is the first release-line core that carries
+           QSessionStoreRegistry.getInstance(QInstance) and clearIfSame, which the
+           application-scoped SHARED_REDIS provider requires (RC.21 and earlier do not compile). -->
+      <qqq.version>4.1.0-RC.22</qqq.version>
+      <!-- Published qbit-redis release candidate whose public api (RedisAccess, RedisCache,
+           RedisNamespace) the SHARED_REDIS provider is built against. -->
+      <qbit-redis.version>0.1.0-RC.1</qbit-redis.version>
   </properties>

   <parent>
@@ -79,7 +85,7 @@
         <dependency>
            <groupId>com.kingsrook.qqq</groupId>
            <artifactId>qqq-bom-pom</artifactId>
-            <version>${qqq.snapshot.version}</version>
+            <version>${qqq.version}</version>
            <type>pom</type>
            <scope>import</scope>
         </dependency>
@@ -95,7 +101,7 @@
      <dependency>
         <groupId>com.kingsrook.qbits</groupId>
         <artifactId>qbit-redis</artifactId>
-         <version>0.1.0-redis-7fe5492-SNAPSHOT</version>
+         <version>${qbit-redis.version}</version>
         <optional>true</optional>
      </dependency>

@@ -111,7 +117,7 @@
      <dependency>
         <groupId>com.kingsrook.qqq</groupId>
         <artifactId>qqq-middleware-javalin</artifactId>
-         <version>${qqq.snapshot.version}</version>
+         <version>${qqq.version}</version>
         <scope>test</scope>
      </dependency>
      <dependency>
@@ -137,7 +143,7 @@
      <dependency>
         <groupId>org.assertj</groupId>
         <artifactId>assertj-core</artifactId>
-         <version>3.27.3</version>
+         <version>3.27.7</version>
         <scope>test</scope>
      </dependency>