ci: release with the service account token - #25
Merged
Conversation
The org ruleset "Run Apify Pull Request Toolkit on every PR" requires that workflow on main, and github-actions is not a bypass actor, so the release job's push to main was rejected. The Service Account team does bypass the ruleset, so use its token for the checkout push and for gh, as other apify repos do. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last release run failed on
git push origin main:The org ruleset Run Apify Pull Request Toolkit on every PR requires that workflow on the default branch. Its bypass actors are OrganizationAdmin, two apps, and the Service Account team —
github-actionsis none of them, so the release job's push can never satisfy the rule.So the release job now authenticates as the service account (
APIFY_SERVICE_ACCOUNT_GITHUB_TOKEN, an org secret already available to this repo), which is how the rest of the apify repos push release commits — seeapify/apify-mcp-server's_update_release_metadata.yaml.A bot-opened release PR was the alternative, but PRs created with
GITHUB_TOKENdon't triggerpull_requestworkflows, so the required check would never run and the PR could not merge.Also adds
[skip ci]to the release commit so a version-only bump doesn't re-run Tests on main.Verified only up to the push: this can't be proven green until the next Release dispatch, which publishes a real version.
🤖 Generated with Claude Code