Skip to content

fix: use RELEASE_PLEASE_TOKEN for release-please action#10

Merged
peter-svensson merged 1 commit intomainfrom
fix/release-please-token
Mar 8, 2026
Merged

fix: use RELEASE_PLEASE_TOKEN for release-please action#10
peter-svensson merged 1 commit intomainfrom
fix/release-please-token

Conversation

@peter-svensson
Copy link
Copy Markdown
Member

Summary

  • Use RELEASE_PLEASE_TOKEN instead of GITHUB_TOKEN for release-please action
  • PRs created with GITHUB_TOKEN don't trigger CI workflows (GitHub prevents events from GITHUB_TOKEN creating new workflow runs)

Test plan

  • Merge and verify release-please PRs trigger CI

PRs created with GITHUB_TOKEN don't trigger CI workflows (GitHub
prevents events from GITHUB_TOKEN creating new workflow runs).
Using a separate token ensures release-please PRs trigger CI.
@peter-svensson peter-svensson enabled auto-merge (squash) March 8, 2026 11:01
@peter-svensson peter-svensson merged commit 4e6278c into main Mar 8, 2026
4 checks passed
@peter-svensson peter-svensson deleted the fix/release-please-token branch March 8, 2026 11:01
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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