QRun-IO/qbit-redis
3
0 Fork 0
Code Issues Pull Requests 2 Actions Packages Projects Releases Wiki Activity

Compare commits

merge into: QRun-IO/qbit-redis:develop
QRun-IO/qbit-redis:develop QRun-IO/qbit-redis:release/0.2 QRun-IO/qbit-redis:release/first-release-20261106 QRun-IO/qbit-redis:release/0.1 QRun-IO/qbit-redis:automation/qbit-rc-pending QRun-IO/qbit-redis:feature/kof22-redis-canonical QRun-IO/qbit-redis:main QRun-IO/qbit-redis:feature/redis-integration-20261029 QRun-IO/qbit-redis:test/redis-topology-1301 QRun-IO/qbit-redis:test/redis-mtls-1317 QRun-IO/qbit-redis:docs/shared-snapshot-handoff QRun-IO/qbit-redis:feature/redis-production-20261021 QRun-IO/qbit-redis:feature/redis QRun-IO/qbit-redis:ci/central-orb-standard
QRun-IO/qbit-redis:v0.2.0-RC.1 QRun-IO/qbit-redis:v0.1.0-RC.1 QRun-IO/qbit-redis:publish-redis-integration-20261029-551f1d5 QRun-IO/qbit-redis:publish-redis-20261021-7fe5492
...
pull from: QRun-IO/qbit-redis:docs/shared-snapshot-handoff
QRun-IO/qbit-redis:release/0.2 QRun-IO/qbit-redis:develop QRun-IO/qbit-redis:release/first-release-20261106 QRun-IO/qbit-redis:release/0.1 QRun-IO/qbit-redis:automation/qbit-rc-pending QRun-IO/qbit-redis:feature/kof22-redis-canonical QRun-IO/qbit-redis:main QRun-IO/qbit-redis:feature/redis-integration-20261029 QRun-IO/qbit-redis:test/redis-topology-1301 QRun-IO/qbit-redis:test/redis-mtls-1317 QRun-IO/qbit-redis:docs/shared-snapshot-handoff QRun-IO/qbit-redis:feature/redis-production-20261021 QRun-IO/qbit-redis:feature/redis QRun-IO/qbit-redis:ci/central-orb-standard
QRun-IO/qbit-redis:v0.2.0-RC.1 QRun-IO/qbit-redis:v0.1.0-RC.1 QRun-IO/qbit-redis:publish-redis-integration-20261029-551f1d5 QRun-IO/qbit-redis:publish-redis-20261021-7fe5492
1 Commits
develop ... docs/shared-snapshot-handoff
Author SHA1 Message Date
james.maesandCodex 01664b0ae4 docs: update shared snapshot publication handoff 
Co-Authored-By: Codex <noreply@openai.com>
 2026-10-22 04:48:42 -05:00
1 changed files with 8 additions and 4 deletions
Expand all files Collapse all files
docs/SNAPSHOT-RELEASE.md
+8 -4
View File
@@ -1,6 +1,6 @@
# Coordinated candidate snapshot
Status: locally verified candidate; remote publication is pending. This is not a production deployment checklist or an RC certification.
Status, 2026-10-22: source is uploaded, canonical branch CI is verified and enforced, and the required Core snapshot is published. Publication of Redis `0.1.0-SNAPSHOT` through the canonical `develop` pipeline remains to be verified. This is not a production deployment checklist or an RC certification.
## Local evidence
@@ -14,12 +14,16 @@ Status: locally verified candidate; remote publication is pending. This is not a
1. Capture reviewed source revisions for the coordinated core, Redis, collaboration, session-store and frontend candidates. Preserve unrelated worktrees and edits.
2. Publish the corresponding QQQ4.1.0-SNAPSHOT parent/BOM and required core modules first. The consumer graph currently includes backend-core, backend-module-rdbms, middleware-javalin and openapi.
3. GitHub repository https://github.com/QRun-IO/qbit-redis now exists PUBLIC, matching the existing collaboration/session-store repositories; it is still empty. Local origin is connected. CircleCI project gh/QRun-IO/qbit-redis was created (ID7c6fe3ea-5281-437a-b188-818d7d83a604). Initial source upload, develop default branch and required context access/pipeline execution remain to be verified. The empty project initially reports main; change it after develop exists.
4. Run Redis CI and publish0.1.0-SNAPSHOT through the standard QBit orb. The local CI config matches the current GitHub collaboration configuration's orb0.7.18 entry point. Authenticated registry lookup confirms this is a private orb and0.7.18 exists. Config validation PASSED with the verified QRun-IO organization ID: `circleci config validate .circleci/config.yml --org bb329fea-03cd-4fb5-b530-15e85703598d`. Earlier missing-orb messages were caused by absent organization context (this new repo has no remote for inference), not a missing release. Use the existing session credential loader and map CIRCLECI_TOKEN to CIRCLE_TOKEN only within the invoking process. Actual Redis project pipeline execution remains unverified. The Redis POM exposes the revision property required by the orb's version script.
3. The public [Redis repository](https://github.com/QRun-IO/qbit-redis) has canonical `main` and `develop` branches; `develop` is the default. [PR #1](https://github.com/QRun-IO/qbit-redis/pull/1) installed the shared orb declarations at `33b21f9c0a1ea316f7f720bbde2465ac11d81af0`. CircleCI pipelines 10 and 11 passed on that revision. Both branches enforce the `setup` and `verify` checks from CircleCI app 18001, including for administrators.
4. Publish `0.1.0-SNAPSHOT` through the shared QBit profile declared in `.qqq-ci.yml`. The canonical caller tracks `kingsrook/qqq-orb@0.8`; the orb owns verification, version calculation, signing and deployment. Normal `develop` changes select snapshot publication. CI-only declaration changes intentionally verify without publishing, so pipelines 10 and 11 do not prove artifact publication. Follow the actual publisher to success and resolve its timestamped POM/JAR from the remote repository before marking this step complete. Do not add a repository-specific publishing workflow.
5. Run and publish collaboration0.1.0-SNAPSHOT and the coordinated session-store/frontend candidates as applicable. Frontend and collaboration lease endpoints require coordinated rollout; do not pair the new frontend with an older backend.
6. Resolve exact published artifacts in a fresh consumer cache, repeat normal host startup/presence/admin checks, and record remote coordinates, source SHAs and artifact checksums. Local cache success is insufficient for this step.
The earlier request authorizes preparing a snapshot when ready. Repository and CI project creation are complete; no source commit/push or artifact publication has occurred. Keep this distinction explicit. Source-only Gitleaks scan passed (no leaks; generated logs and local evidence were not included in that scan).
## Verified dependency baseline
Core commit `47eb326c4a36e481a8cf36b93c2e022760d08c76` completed publisher job 9606. Its published `4.1.0-SNAPSHOT` artifacts were checked remotely: 19 resolved POMs and the backend-core/Javalin JAR APIs needed by Redis (`getIfStarted`, message audience accessors, audience-provider configuration and hub audience filtering). Redis pipeline 8 then passed against the published dependency before PR #1 merged.
This baseline establishes the Core dependency and Redis CI path. It does not certify the coordinated collaboration/session-store/frontend deployment or a stable Redis release. Retain the separate consumer and host checks in steps 5 and 6.
## Operational scope