ci: centralize release branch verification and workflows #74

2026-10-21T17:34:07Z

KofTwentyTwo commented

2026-10-21 17:34:07 +00:00

(Migrated from github.com)

Replace the legacy release/0.1.0 CI graph with the published and registry-verified orb0.7.16 manifest, canonical RC caller, and shared scanner. Preserve the existing application release and tag policy.

This refresh is based on the completed dependency repair and verified Maven Central publication of 0.1.0-RC.2. The signed one-parent CI-only commit leaves the released application POM unchanged and renders only the normal Maven test job on the release branch, without publishing another application version. Canonical validation, actionlint, diff checks, and actual-commit pipeline selection passed. Hosted setup, verify and shared scanning must pass before the normal merge and post-merge enforcement audit.

Replace the legacy release/0.1.0 CI graph with the published and registry-verified orb0.7.16 manifest, canonical RC caller, and shared scanner. Preserve the existing application release and tag policy. This refresh is based on the completed dependency repair and verified Maven Central publication of 0.1.0-RC.2. The signed one-parent CI-only commit leaves the released application POM unchanged and renders only the normal Maven test job on the release branch, without publishing another application version. Canonical validation, actionlint, diff checks, and actual-commit pipeline selection passed. Hosted setup, verify and shared scanning must pass before the normal merge and post-merge enforcement audit.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-quick-search#74