fix: trigger release PR checks with SDK App token

[nickcollisson-workos]

Use the SDK automation App to create release PRs so GitHub starts their CI and required release workflow. The previous default 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 Node 20/22/24 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.

[greptile-apps]

Confidence Score: 5/5

[Critical impact] The PR appears safe to merge; no actionable issue was found.

Summary

Updates .github/workflows/release.yml to create an SDK App token and pass it to release-please, so release PRs can trigger CI and required workflows.

• Requests write access to contents and pull requests.
• Keeps the existing release output and publish condition.
• No actionable issues found.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Push[Push to main] --> Token[Create SDK App token]
  Token --> Release[Run release-please]
  Release --> PR[Create or update release PR]
  PR --> CI[PR checks]
  Release --> Gate{Release created?}
  Gate -->|Yes| Publish[Publish package]

Loading

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