ci: adopt managed orb and shared maintenance callers #1

Merged
KofTwentyTwo merged 1 commits from ci/central-orb-standard into feature/redis-production-20261021 2026-10-22 09:22:59 +00:00
KofTwentyTwo commented 2026-10-21 22:02:59 +00:00 (Migrated from github.com)

Use the managed 0.8 orb track and the same immutable shared CodeQL and RC callers as other QBits. All runtime build/release/scanner logic remains owned by qqq-orb; these changes contain only the manifest, setup caller and two canonical workflow bridges.

Canonical rollout and scanner/RC validation pass. Existing Redis CI fails compilation because the published Core dependency lacks expected realtime APIs. That failure remains a merge blocker; this PR does not alter application source, waive tests, or publish an artifact.

The repository currently has only feature/redis-production-20261021, so this PR targets that existing branch. The manifest declares develop; canonical branch bootstrap/default selection and merge protection remain outstanding after the coordinated Core dependency is resolved. Default CodeQL setup was read as not-configured before adding the shared caller; no scanner setting was disabled.

Use the managed 0.8 orb track and the same immutable shared CodeQL and RC callers as other QBits. All runtime build/release/scanner logic remains owned by qqq-orb; these changes contain only the manifest, setup caller and two canonical workflow bridges. Canonical rollout and scanner/RC validation pass. Existing Redis CI fails compilation because the published Core dependency lacks expected realtime APIs. That failure remains a merge blocker; this PR does not alter application source, waive tests, or publish an artifact. The repository currently has only feature/redis-production-20261021, so this PR targets that existing branch. The manifest declares develop; canonical branch bootstrap/default selection and merge protection remain outstanding after the coordinated Core dependency is resolved. Default CodeQL setup was read as not-configured before adding the shared caller; no scanner setting was disabled.
github-advanced-security[bot] commented 2026-10-21 22:04:53 +00:00 (Migrated from github.com)

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. ### What Enabling Code Scanning Means: - The 'Security' tab will display more code scanning analysis results (e.g., for the default branch). - Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. - You will be able to see the analysis results for the pull request's branch on this [overview](/QRun-IO/qbit-redis/security/code-scanning?query=pr%3A1+is%3Aopen) once the scans have completed and the checks have passed. For more information about GitHub Code Scanning, check out [the documentation](https://docs.github.com/code-security/code-scanning/introduction-to-code-scanning/about-code-scanning).
Sign in to join this conversation.