Skip to content

[v5r0] chore: release with a deploy key - #835

Closed
aldbr wants to merge 1 commit into
DIRACGrid:rel-v5r0from
aldbr:ci/release-deploy-key-rel-v5r0
Closed

aldbr wants to merge 1 commit into
DIRACGrid:rel-v5r0from
aldbr:ci/release-deploy-key-rel-v5r0

Conversation

@aldbr

@aldbr aldbr commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Part of DIRACGrid/.github#5.

The release job pushes commits and a tag from CI, which the branches and tags rulesets now reject. Port of #834; also removes the reference to the non-existent secrets.PAT.

  • Commits and tag are pushed with a write deploy key (RELEASE_DEPLOY_KEY, environment release, release branches only, workflow_dispatch only). Deploy keys are the bypass actor of both rulesets.
  • The GitHub release is created with the GITHUB_TOKEN on 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

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
aldbr force-pushed the ci/release-deploy-key-rel-v5r0 branch from c23f4a0 to c9404f8 Compare November 20, 2026 10:54
@aldbr aldbr changed the title [v5r0] ci: release with a deploy key [v5r0] chore: release with a deploy key Nov 20, 2026
@aldbr

aldbr commented Nov 20, 2026

Copy link
Copy Markdown
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.

@aldbr aldbr closed this Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant