Skip to content

fix: trigger release PR checks with SDK App token - #18

Merged
nicknisi merged 2 commits into
mainfrom
nickcollisson/release-app-token
Oct 19, 2026
Merged

nicknisi merged 2 commits into
mainfrom
nickcollisson/release-app-token

Conversation

@nickcollisson-workos

@nickcollisson-workos nickcollisson-workos commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Use the SDK automation App to create release PRs so GitHub starts their CI and required release workflow. The previous GITHUB_TOKEN does not trigger ruleset workflows.

The App is now installed on this repository, and its existing organization credentials are available. The token is restricted to this repository with contents and pull-request write permissions, matching the other SDKs.

CI passes, including lint, typecheck, build, and Electron end-to-end tests. The organization's Release policy workflow also passed on this PR in Evaluate mode. After merge, the next release-please update will verify the App-created release trigger.

@nickcollisson-workos
nickcollisson-workos requested a review from a team as a code owner October 8, 2026 21:20
@greptile-apps

greptile-apps Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

RetriggerConfidence Score: 5/5

[Critical impact] The PR appears safe to merge; no actionable issue was found in the token change or the workflows it starts.

Summary

Changes .github/workflows/release-please.yml to create an SDK App token and pass it to release-please, so release pull requests can start CI and required workflows.

  • Requests write access to contents and pull requests.
  • Leaves the existing publish job and its credentials unchanged.
  • No actionable issues found.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
  A[Push to main] --> B[Create SDK App token]
  B --> C[Run release-please]
  C --> D[Open or update release PR]
  D --> E[Start PR checks]
  C --> F{Release created?}
  F -->|Yes| G[Call existing publish workflow]
Loading

Reviews (1) · Last reviewed commit: "docs: explain why release automation use..." · Reviewed by Greptile

@workos-shipyard

Copy link
Copy Markdown

⚓ Shipyard review suggestion

Suggested team: applied-ai, based on recent contributors to the changed files (@nicknisi).

Links open Shipyard for confirmation. Choosing a reviewer overrides availability; “Pick for me” skips known absences.
Comment /tag <team> for a team or /tag to infer one. Tag the same team again to reroll.

Shipyard Analysis

⏳ Generating analysis...

⚓ Explore the analysis in depth in Shipyard · 🔄 Re-run analysis

@nicknisi
nicknisi merged commit 84cf42d into main Oct 19, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants