feat(redis): integrate qualified Redis topology work on QQQ 4.1.0-RC.21 #8

Merged
james.maes merged 12 commits from feature/kof22-redis-canonical into develop 2026-11-05 17:02:38 +00:00
Owner

Lands the qualified Redis topology integration on develop against the published QQQ core.

  • Merges the owner's feature/redis-integration-20261029 (551f1d5) into develop (7152f0a6) and adds the five qualification fixtures (FixtureEndpoint and its test, plus edits to RedisPromotionTest, RedisAuthenticationTest and RedisPartitionHealingTest).
  • cc9c3d28 repins the BOM to the published qqq-bom-pom 4.1.0-RC.21 (Maven Central), replacing the pending 4.1.0-SNAPSHOT property. Redis needs no API newer than RC.21: the 16 main and 14 test sources compile with zero errors under javac against the published RC.21 jars plus Jedis 7.2.0. The qualification of the fixtures against RC.21 is the native check of this PR.
  • Nothing is published from this PR. After the checks pass and the head is stable it merges normally; the RC is cut afterwards with the existing release-rc workflow (revision 0.1.0-SNAPSHOT gives release/0.1, 0.1.0-RC.1).

🤖 Generated with Claude Code

Lands the qualified Redis topology integration on `develop` against the published QQQ core. - Merges the owner's `feature/redis-integration-20261029` (`551f1d5`) into `develop` (`7152f0a6`) and adds the five qualification fixtures (FixtureEndpoint and its test, plus edits to RedisPromotionTest, RedisAuthenticationTest and RedisPartitionHealingTest). - `cc9c3d28` repins the BOM to the published `qqq-bom-pom 4.1.0-RC.21` (Maven Central), replacing the pending `4.1.0-SNAPSHOT` property. Redis needs no API newer than RC.21: the 16 main and 14 test sources compile with zero errors under `javac` against the published RC.21 jars plus Jedis 7.2.0. The qualification of the fixtures against RC.21 is the native check of this PR. - Nothing is published from this PR. After the checks pass and the head is stable it merges normally; the RC is cut afterwards with the existing `release-rc` workflow (revision `0.1.0-SNAPSHOT` gives `release/0.1`, `0.1.0-RC.1`). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
james.maes added 12 commits 2026-11-05 16:30:14 +00:00
Use existing publish-tag support to produce isolated candidate coordinates without merging into develop. Setup configs validated; session-store moves to orb0.7.18 for QBit feature support. Exact prerequisite versions and artifact publication remain pending.

Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Require separate trusted client keys with real Redis TLS, reject missing and unrelated identities, and verify framework health after authenticated startup. Full verify passes24tests and coverage gates. No production runtime changes.

Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: GPT-6 (Codex) <noreply@openai.com>
Co-Authored-By: Codex (GPT-6) <noreply@openai.com>
Merges feature/redis-integration-20261029 (endpoint switching, write health,
pool recovery, mTLS/promotion/partition qualification, feature-snapshot CI
tag filter) into current develop b1fd263 and adds the endpoint fixture and
test adjustments used by the host acceptance runs (FixtureEndpoint(+Test),
RedisPromotionTest, RedisAuthenticationTest, RedisPartitionHealingTest).

Conflict choices: docs/SNAPSHOT-RELEASE.md keeps develop's current text;
the core dependency stays on the canonical 4.1.0-SNAPSHOT line (the
feature-snapshot pin is not carried) with a marker to repin to the
published core version after the core integration PR is released.
No PRIVATE or feature-snapshot coordinate is introduced.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
build: depend on the published QQQ 4.1.0-RC.21 core
QRun-IO/ci-policy: ci / fork-guard (pull_request) Skipped
QRun-IO/ci-policy: native / fork-deny (pull_request) Skipped
QRun-IO/ci-policy: native / dotnet-0 (pull_request) Skipped
Shared Java Maven CI with Docker / secrets (push) Successful in 15s
QRun-IO/ci-policy: ci / Scoped workflow [workflow 5e6bfd71ee8a5674882f7680c695a0ada599622f] (pull_request) Successful in 6s
QRun-IO/ci-policy: ci / head-profile (pull_request) Skipped
QRun-IO/ci-policy: ci / repository-policy (pull_request) Skipped
QRun-IO/ci-policy: ci / application-template-0 (pull_request) Skipped
QRun-IO/ci-policy: ci / gradle-1 (pull_request) Skipped
QRun-IO/ci-policy: ci / java-core-2-head (pull_request) Skipped
QRun-IO/ci-policy: ci / java-docker-3 (pull_request) Skipped
QRun-IO/ci-policy: ci / java-docker-3-head (pull_request) Skipped
QRun-IO/ci-policy: ci / java-frontend-browser-5 (pull_request) Skipped
QRun-IO/ci-policy: ci / java-maven-6 (pull_request) Skipped
QRun-IO/ci-policy: ci / java-maven-6-head (pull_request) Skipped
QRun-IO/ci-policy: ci / java-maven-7 (pull_request) Skipped
QRun-IO/ci-policy: ci / java-maven-7-head (pull_request) Skipped
QRun-IO/ci-policy: ci / node-8 (pull_request) Skipped
QRun-IO/ci-policy: native / native-result (pull_request) Successful in 7s
QRun-IO/ci-policy: ci / node-9 (pull_request) Skipped
QRun-IO/ci-policy: ci / node-10 (pull_request) Skipped
QRun-IO/ci-policy: ci / node-playwright-11 (pull_request) Skipped
QRun-IO/ci-policy: ci / repository-policy-12 (pull_request) Skipped
QRun-IO/ci-policy: ci / source-config-13 (pull_request) Skipped
QRun-IO/ci-policy: ci / source-config-14 (pull_request) Skipped
QRun-IO/ci-policy: ci / android-0 (pull_request) Skipped
QRun-IO/ci-policy: ci / original-business (pull_request) Skipped
QRun-IO/ci-policy: ci / original-mcp (pull_request) Skipped
QRun-IO/ci-policy: ci / original-voyage (pull_request) Skipped
QRun-IO/ci-policy: ci / original-cli (pull_request) Skipped
QRun-IO/ci-policy: ci / not-enrolled (pull_request) Skipped
QRun-IO/ci-policy: ci / shared-pipeline (pull_request) Skipped
QRun-IO/ci-policy: Shared Java Maven CI with Docker / secrets (pull_request) Successful in 19s
Shared Java Maven CI with Docker / gate (push) Canceled after 0s
Shared Java Maven CI with Docker / verify (push) Canceled after 0s
qrun-release / release (push) Canceled after 17m43s
qrun-release / postpublish (push) Canceled after 0s
QRun-IO/ci-policy: Shared Java Maven CI with Docker / verify (pull_request) Successful in 2m34s
QRun-IO/ci-policy: Shared Java Maven CI with Docker / gate (pull_request) Successful in 13s
QRun-IO/ci-policy: ci / java-docker-4 (pull_request) Successful in 22m56s
QRun-IO/ci-policy: ci / ci-result (pull_request) Successful in 6s
Release candidate / release-rc (pull_request) Skipped
cc9c3d280c
Replace the pending 4.1.0-SNAPSHOT property with the published qqq-bom-pom 4.1.0-RC.21
(Maven Central) as the one BOM version. Redis needs no core API newer than that release:
the main (16) and test (14) sources compile with zero errors under javac against the
published RC.21 jars plus Jedis 7.2.0, so no feature is dropped and nothing is guessed.
The QQQ BOM and the parent's JUnit BOM are on the same 6.0 line. README wording updated;
the historical snapshot-release record is unchanged.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
james.maes merged commit 4f169f2a7b into develop 2026-11-05 17:02:38 +00:00
Sign in to join this conversation.