Repository navigation
Conversation
The branch and tag rulesets only let deploy keys through, so the release notes commit and the tag are pushed with a write deploy key that lives in the `release` environment (release branches only, workflow_dispatch only). The GitHub release is then created on the existing tag with the GITHUB_TOKEN. Assisted-by: Claude:claude-fable-5-2
aldbr
force-pushed
the
ci/release-deploy-key-rel-v5r0
branch
from
November 20, 2026 10:54
c23f4a0 to
c9404f8
Compare
Contributor
Author
|
Superseded: releases will follow "CI drafts, a release manager publishes, CI ships" with no stored write credential (DIRACGrid/.github#5). The deploy key, its environment and the ruleset bypass have been removed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of DIRACGrid/.github#5.
The release job pushes commits and a tag from CI, which the
branchesandtagsrulesets now reject. Port of #834; also removes the reference to the non-existentsecrets.PAT.RELEASE_DEPLOY_KEY, environmentrelease, release branches only,workflow_dispatchonly). Deploy keys are the bypass actor of both rulesets.GITHUB_TOKENon the existing tag.Same push step as DIRACGrid/DIRAC#8931, which was run end to end in a fork. This workflow itself was not run.
The environment, key and ruleset bypass are already in place (
scripts/setup_release_key.py, DIRACGrid/.github#13).🤖 Generated with Claude Code