ci: enroll shared Gitea release-candidate lifecycle #56

Merged

forge-recovery merged 1 commits from ci-qrun-rc-caller-20261102 into develop 2026-11-02 21:31:07 +00:00

Conversation 0 Commits 1 Files Changed 1

+72

forge-recovery commented 2026-11-02 20:14:30 +00:00

Owner

Copy link

Copy source

Restore the existing release-candidate entrypoint through the protected shared Gitea lifecycle. The caller is identical across the33 already-authorized release_completion repositories.

Preserves all8 original manual inputs, their types/defaults, and the closed/merged develop PR release:rc label guard. The existing proven workflow_dispatch finalize/recover callback replaces repository_dispatch. Only the already-bound QRUN_TAG_SIGNING_KEY is forwarded; Central/GPG credentials stay in the trusted publisher. Default contents permission remains read, with the existing isolated shared release job using contents/write, actions/read and pull-requests/write. No application code, versions, old GitHub workflow, credential values or new roles change.

The identical contract was checked against all33 original callers and the current protected qbit-release-rc.yaml/b068 trusted-receipt callee. Actual configured PR checks must pass before normal merge; this PR does not cut or publish an artificial release.

Restore the existing release-candidate entrypoint through the protected shared Gitea lifecycle. The caller is identical across the33 already-authorized release_completion repositories. Preserves all8 original manual inputs, their types/defaults, and the closed/merged develop PR release:rc label guard. The existing proven workflow_dispatch finalize/recover callback replaces repository_dispatch. Only the already-bound QRUN_TAG_SIGNING_KEY is forwarded; Central/GPG credentials stay in the trusted publisher. Default contents permission remains read, with the existing isolated shared release job using contents/write, actions/read and pull-requests/write. No application code, versions, old GitHub workflow, credential values or new roles change. The identical contract was checked against all33 original callers and the current protected qbit-release-rc.yaml/b068 trusted-receipt callee. Actual configured PR checks must pass before normal merge; this PR does not cut or publish an artificial release.

forge-recovery added 1 commit 2026-11-02 20:14:30 +00:00

ci: enroll shared Gitea release-candidate lifecycle ... 594e755da4

Co-Authored-By: Codex <noreply@openai.com>

forge-recovery merged commit 6e60585af1 into develop 2026-11-02 21:31:07 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

Clear labels

architecture

Architecture review: coupling, cohesion, UI API

bug

Something isn't working

dependencies

documentation

Improvements or additions to documentation

duplicate

This issue or pull request already exists

enhancement

New feature or request

github_actions

Pull requests that update GitHub Actions code

good first issue

Good for newcomers

help wanted

Extra attention is needed

invalid

This doesn't seem right

java

Pull requests that update java code

question

Further information is requested

secuurity

wontfix

This will not be worked on

No labels

Milestone

No items

No Milestone

Projects

Clear projects

No projects

Assignees

Clear assignees

forge-recovery (Forge Recovery) james.maes (James Maes)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: QRun-IO/qbit-collaboration#56