Local video editor for coding agents: 42 FFmpeg tools with a machine-readable contract and an MCP server, for Claude Code, Cursor and Codex. Cut, captions, reframe, loudness, platform exports. No cloud, no API keys.
Python agent-skillsai-agentsaudio-processingcaptionsclaude-codecodexcoding-agentcursorffmpegloudness-normalizationmcpmcp-servermodel-context-protocolpythonsubtitlestranscodingvideovideo-editingvideo-processingwhisper
ci(release): push the bump commit with RELEASE_PUSH_TOKEN so the main ruleset lets it through (#170)
Shogo Kajiyama0ad535d20f3f
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex dfc86ba..2eb3845 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -35,6 +35,17 @@ name: release# the auto-bump commit below is safe to push straight from this job without# looping: it never starts a second run of this workflow, this same run just# continues on past it with the new version.+#+# main is protected by a ruleset (PR required, 8 status checks) that the+# built-in GITHUB_TOKEN cannot bypass (GitHub Actions is not an accepted+# bypass actor; #137). The bump commit is therefore pushed with the+# RELEASE_PUSH_TOKEN secret when it exists: a fine-grained PAT of a repository+# admin (Contents: read/write on this repo only), whose "Repository admin"+# bypass lets the push through. A PAT push DOES trigger workflows, unlike+# GITHUB_TOKEN, so the bump commit message carries [skip ci]: the tag, the+# GitHub Release and the npm publish all happen in this same run, and a second+# run on the bump commit would only find the tag already present. Without the+# secret the push falls back to GITHUB_TOKEN (works on an unprotected main).on:push:@@ -59,6 +70,7 @@ jobs:- uses: actions/checkout@v4with:fetch-depth: 0+ token: ${{ secrets.RELEASE_PUSH_TOKEN || secrets.GITHUB_TOKEN }}- name: Decide whether an automatic version bump is neededid: setup@@ -183,7 +195,7 @@ jobs:git config user.name "github-actions[bot]"git config user.email "github-actions[bot]@users.noreply.github.com"git add package.json .claude-plugin/plugin.json docs/contract.md CHANGELOG.md- git commit -m "chore(release): bump version to ${NEW_VERSION}"+ git commit -m "chore(release): bump version to ${NEW_VERSION} [skip ci]"git push origin HEAD:main- name: Check whether this version is already releaseddiff --git a/references/process-pitfalls.md b/references/process-pitfalls.mdindex 3063128..73abdc6 100644--- a/references/process-pitfalls.md+++ b/references/process-pitfalls.md@@ -168,3 +168,15 @@ before the push, the tag or the publish -- a clean no-op, but a red run and no rscript now takes whatever sits under Unreleased into the new version's section and puts theplaceholder back, so hand-written notes are welcome there. Lesson: an anchor that is alsoprose will be edited; anchor on the heading, not on the placeholder text.++### The built-in GITHUB_TOKEN cannot push the release bump through a ruleset++Found on the first release after the main ruleset went active (2026-09-11, run for #166):+`git push origin HEAD:main` from release.yml was declined with GH013 ("Changes must be made+through a pull request", "8 of 8 required status checks are expected"). GitHub Actions cannot+be added as a ruleset bypass actor (the import rejects the actor, the UI does not list it), so+the bump push now uses the `RELEASE_PUSH_TOKEN` secret -- a fine-grained PAT of a repository+admin with Contents: read/write on this repo -- whose "Repository admin" bypass applies. A PAT+push triggers workflows (GITHUB_TOKEN's do not), so the bump commit carries `[skip ci]`; the+tag, Release and npm publish all happen in the originating run. Rotate the PAT before it+expires or the next release fails at the same step, cleanly, before anything is published.