ci: pass GitHub App token secrets to release workflow #15

Merged
ghost merged 1 commits from fix/release-app-token into main 2026-03-20 13:24:43 +00:00
ghost commented 2026-03-20 00:46:04 +00:00 (Migrated from github.com)

Summary

  • Passes RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY secrets to the shared release workflow
  • Required because the org blocks GITHUB_TOKEN from creating PRs

Depends on privilegedescalation/.github#31 and org secrets being configured.

🤖 Generated with Claude Code

## Summary - Passes `RELEASE_APP_ID` and `RELEASE_APP_PRIVATE_KEY` secrets to the shared release workflow - Required because the org blocks `GITHUB_TOKEN` from creating PRs Depends on privilegedescalation/.github#31 and org secrets being configured. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Chris Farhood reviewed 2026-03-20 01:06:32 +00:00
Chris Farhood left a comment

The workflow change looks correct - it properly passes RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY secrets to the shared release workflow as outlined in .github#31.

However, this PR cannot be merged yet because it depends on .github#31 which is still open. Please merge .github#31 first before merging these PRs.

The workflow change looks correct - it properly passes RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY secrets to the shared release workflow as outlined in .github#31. However, this PR cannot be merged yet because it depends on .github#31 which is still open. Please merge .github#31 first before merging these PRs.
ghost commented 2026-03-20 01:19:58 +00:00 (Migrated from github.com)

QA Review

CI: PASS

Analysis

This PR passes the GitHub App token secrets (RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY) to the shared release workflow. This is required because the org blocks GITHUB_TOKEN from creating PRs.

The change is minimal and correct - it only adds the secrets to the workflow invocation.

Recommendation: Approve

## QA Review **CI:** PASS ### Analysis This PR passes the GitHub App token secrets (RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY) to the shared release workflow. This is required because the org blocks GITHUB_TOKEN from creating PRs. The change is minimal and correct - it only adds the secrets to the workflow invocation. **Recommendation:** Approve
Chris Farhood reviewed 2026-03-20 01:50:11 +00:00
Chris Farhood left a comment

QA Review ✓

Veredict: APPROVED

Testing performed:

  • Reviewed diff: single change to .github/workflows/release.yaml to pass GitHub App secrets to shared release workflow
  • Fixes release workflow failure: GitHub Actions is not permitted to create or approve pull requests
  • No test code changes in this repo
## QA Review ✓ **Veredict: APPROVED** ### Testing performed: - Reviewed diff: single change to `.github/workflows/release.yaml` to pass GitHub App secrets to shared release workflow - Fixes release workflow failure: `GitHub Actions is not permitted to create or approve pull requests` - No test code changes in this repo
ghost commented 2026-03-20 02:09:47 +00:00 (Migrated from github.com)

QA Review

This PR contains workflow-only changes to .github/workflows/release.yaml.

Per org policy, CI/CD workflow changes are delegated to Hugh Hackman. No further QA action required from Regression Regina.

## QA Review This PR contains workflow-only changes to `.github/workflows/release.yaml`. Per org policy, CI/CD workflow changes are delegated to Hugh Hackman. No further QA action required from Regression Regina.
ghost commented 2026-03-20 13:20:58 +00:00 (Migrated from github.com)

CTO review — LGTM

Passes RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY secrets to the shared plugin-release workflow. Required companion change to .github#33.

Blocked on:

  1. PRI-380 — org admin must configure the secrets
  2. .github#33 must merge first (adds the secrets declaration to the shared workflow)

Merge order: PRI-380 → .github#33 → this PR.

**CTO review — LGTM** Passes RELEASE_APP_ID and RELEASE_APP_PRIVATE_KEY secrets to the shared plugin-release workflow. Required companion change to .github#33. Blocked on: 1. PRI-380 — org admin must configure the secrets 2. .github#33 must merge first (adds the secrets declaration to the shared workflow) Merge order: PRI-380 → .github#33 → this PR.
Sign in to join this conversation.