Skip to content

fix(ci): wire release-please PAT into release workflow#27

Merged
OgeonX-Ai merged 1 commit into
mainfrom
codex/release-please-rollout-autopilot-core-20260713
Jul 13, 2026
Merged

fix(ci): wire release-please PAT into release workflow#27
OgeonX-Ai merged 1 commit into
mainfrom
codex/release-please-rollout-autopilot-core-20260713

Conversation

@OgeonX-Ai

Copy link
Copy Markdown
Contributor

Summary

Update the release-please caller workflow to use the merged org reusable workflow commit and pass RELEASE_PLEASE_TOKEN explicitly.

Changes

  • pin the reusable workflow call to .github commit 320a99a4c15487786dc73827ba7416303ab3fd1b
  • pass secrets.RELEASE_PLEASE_TOKEN into the reusable workflow

Why

GitHub Actions on these repos cannot create release PRs with the default token alone. The reusable workflow now supports an explicit PAT fallback, so the caller must pass it.

Validation

  • compared the live default-branch workflow against the prepared local workflow
  • verified repo-level RELEASE_PLEASE_TOKEN exists before opening this PR
  • verified the canary rollout succeeded on the same reusable workflow SHA

Risks

This changes the release automation path on the default branch. The expected follow-up signal is a fresh Release Please workflow run after merge.

Related

Follows .github PR #24 and the successful canary rollout in autogen and gsd-orchestrator.

Reviewer notes

Start with .github/workflows/release-please.yml; the change is intentionally limited to one workflow file.

@OgeonX-Ai OgeonX-Ai merged commit bac9ea0 into main Jul 13, 2026
2 checks passed
@OgeonX-Ai OgeonX-Ai deleted the codex/release-please-rollout-autopilot-core-20260713 branch July 13, 2026 09:32
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