Skip to content

ci: remove organization-specific App secret naming from release Actions - #163

Draft
vitormattos wants to merge 1 commit into
mainfrom
ci/generic-release-app-key-diagnostics-20261118
Draft

vitormattos wants to merge 1 commit into
mainfrom
ci/generic-release-app-key-diagnostics-20261118

Conversation

@vitormattos

Copy link
Copy Markdown
Member

Summary

  • Make the required GitHub App key diagnostic neutral in the prepare and post-merge reusable Actions.
  • Do not assume any specific repository secret name: the consumer provides the app-private-key input from its own configured Actions secret.
  • Preserve all release logic, permissions, Action input contracts and security checks; only diagnostic text changes.

Validation and deployment

  • Signed DCO commit; workflow/Action CI checks need review before merge.
  • Consumers are being migrated to generic GitHub App secret references in separate PRs. Pinned release-tool Actions continue using their existing commit until a normal reviewed version update.
  • No merge or release requested.

Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
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