ci: publish the current SFTP source as an immutable RC #31
Merged
james.maes
merged 2 commits from 2026-11-05 17:22:21 +00:00
feature/kof22-sftp-rc into develop
2
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
  james.maesandClaude Sonnet 5.5
|
537e8c79f5
|
ci: leave release branches to the shared pipeline in the legacy caller guard
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
QRun-IO/ci-policy: ci / Scoped workflow [workflow 5e6bfd71ee8a5674882f7680c695a0ada599622f] (pull_request) Successful in 7s
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-docker-4 (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: 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: native / native-result (pull_request) Successful in 5s
Shared Java Maven CI / secrets (push) Successful in 19s
QRun-IO/ci-policy: Shared pipeline / Prepare plan [workflow 5e6bfd71ee8a5674882f7680c695a0ada599622f] (pull_request) Successful in 29s
Shared Java Maven CI / verify (push) Successful in 1m15s
QRun-IO/ci-policy: Shared pipeline / Secret scan (pull_request) Successful in 17s
Shared Java Maven CI / gate (push) Successful in 13s
qrun-release / release (push) Successful in 2m3s
qrun-release / postpublish (push) Skipped
QRun-IO/ci-policy: Shared pipeline / Verify library / Linux / Java 21 (pull_request) Successful in 45s
QRun-IO/ci-policy: Shared pipeline / Report (pull_request) Successful in 6s
QRun-IO/ci-policy: ci / shared-pipeline (pull_request) Successful in 2m0s
QRun-IO/ci-policy: Shared pipeline / Release tag (pull_request) Skipped
QRun-IO/ci-policy: ci / ci-result (pull_request) Successful in 5s
QRun-IO/ci-policy: Shared pipeline / Verify ${{ matrix.display }} (pull_request) Skipped
Release candidate / release-rc (pull_request) Skipped
The legacy caller already skips develop because the shared pipeline publishes it. A push to release/X.Y would otherwise start the retired producer next to the shared release-candidate channel and publish the same RC twice. Skip release/* the same way. Needs CI-owner review: the file is the standard thin caller (its sha256 is an enrolled workflow identity of the legacy route, which is retired for this repository). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |
||
|
james.maesandClaude Sonnet 5.5
|
992c7d5a61
|
ci: add the release-candidate channel to the shared SFTP pipeline
Declare a release-candidate channel (push to release/*, versioning maven-release, effective version rule rc-from-branch, central completion and the same source write-back policy as the snapshot channel) and publish it to the existing qrun-maven destination alongside the snapshot channel. The snapshot channel, verification pushes, component, build commands (including flattening) and artifact paths are unchanged. The operator enrollment of the destination must also grant the release-candidate channel before anything publishes. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> |