Ticket t-mmyx6d0xfp0x (W9). cascade-from pushes the FROM bump straight to the target's main. fritzlab/runner, fritzlab/base-dev and fritzlab/base-agent protect main against every push (enable_push: false, no ci-bot allowlist), so the push is refused three times and the upstream release job fails:
base-dev release runs 20 (2026-08-24) and 22 (2026-10-16): Not allowed to push to protected branch main on fritzlab/runner. The base-agent step after it never ran, so base-agent stayed on base-dev:20 and the Agent image never got base:41's AgentHub Secrets hook.
base release run 41 (2026-09-26): the same refusal on fritzlab/base-dev (worked around by hand in base-dev#8).
fritzlab/agent allowlists ci-bot, so base-agent's cascade to it works and keeps working unchanged.
Change: when the push is refused for branch protection, push the commit to cascade/<name>-<tag> and open a pull request against main with the same title. A re-run reuses the branch and treats the 409 for an existing pull request as success. Any other API answer fails the step as before. The script moves out of action.yaml into cascade.sh (same pattern as action/check-naming) so it can be tested.
Tests
New tests/run (CI: .gitea/workflows/test.yaml, as in check-naming) drives cascade.sh against local bare repositories, with a pre-receive hook standing in for branch protection and tests/bin/curl for the Gitea API. Run inside fritzlab/base-dev:20 (the runner's toolchain):
after: 5 passed, 0 failed
before (same tests, original inline script): 2 passed, 3 failed (protected main gets a pull request, a re-run reuses the open pull request, a refused pull request fails the step)
Rollout
Consumers pin @v1, so this takes effect only when the v1 tag is moved to the merge commit (git tag -f v1 <sha> && git push -f origin v1). No consumer workflow changes. The next cascade into a protected repository then opens a pull request that goes through normal review.
The alternative is a forge setting, not code: allowlist ci-bot for direct pushes on runner, base-dev and base-agent the way fritzlab/agent and the playbooks new_protection default already do. That lets bumps land unreviewed; this PR keeps review.
## What and why
Ticket t-mmyx6d0xfp0x (W9). `cascade-from` pushes the FROM bump straight to the target's `main`. fritzlab/runner, fritzlab/base-dev and fritzlab/base-agent protect `main` against every push (`enable_push: false`, no ci-bot allowlist), so the push is refused three times and the upstream release job fails:
- base-dev release runs 20 (2026-08-24) and 22 (2026-10-16): `Not allowed to push to protected branch main` on fritzlab/runner. The base-agent step after it never ran, so base-agent stayed on base-dev:20 and the Agent image never got base:41's AgentHub Secrets hook.
- base release run 41 (2026-09-26): the same refusal on fritzlab/base-dev (worked around by hand in base-dev#8).
fritzlab/agent allowlists ci-bot, so base-agent's cascade to it works and keeps working unchanged.
Change: when the push is refused for branch protection, push the commit to `cascade/<name>-<tag>` and open a pull request against `main` with the same title. A re-run reuses the branch and treats the 409 for an existing pull request as success. Any other API answer fails the step as before. The script moves out of `action.yaml` into `cascade.sh` (same pattern as action/check-naming) so it can be tested.
## Tests
New `tests/run` (CI: `.gitea/workflows/test.yaml`, as in check-naming) drives `cascade.sh` against local bare repositories, with a pre-receive hook standing in for branch protection and `tests/bin/curl` for the Gitea API. Run inside `fritzlab/base-dev:20` (the runner's toolchain):
- after: 5 passed, 0 failed
- before (same tests, original inline script): 2 passed, 3 failed (`protected main gets a pull request`, `a re-run reuses the open pull request`, `a refused pull request fails the step`)
## Rollout
Consumers pin `@v1`, so this takes effect only when the `v1` tag is moved to the merge commit (`git tag -f v1 <sha> && git push -f origin v1`). No consumer workflow changes. The next cascade into a protected repository then opens a pull request that goes through normal review.
The alternative is a forge setting, not code: allowlist ci-bot for direct pushes on runner, base-dev and base-agent the way fritzlab/agent and the playbooks `new_protection` default already do. That lets bumps land unreviewed; this PR keeps review.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Every cascade from base and base-dev has failed since August: runner,
base-dev and base-agent protect main against all pushes, so the direct
push is refused three times and the release job fails, and a refused
first target also skips the next cascade step. Push the bump to
cascade/<name>-<tag> and open a pull request instead, so it lands
through the target's review. Targets that still allow ci-bot to push
(fritzlab/agent) keep the direct push.
The script moves out of action.yaml into cascade.sh so tests/run can
drive it against local bare repositories and a stubbed API.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What and why
Ticket t-mmyx6d0xfp0x (W9).
cascade-frompushes the FROM bump straight to the target'smain. fritzlab/runner, fritzlab/base-dev and fritzlab/base-agent protectmainagainst every push (enable_push: false, no ci-bot allowlist), so the push is refused three times and the upstream release job fails:Not allowed to push to protected branch mainon fritzlab/runner. The base-agent step after it never ran, so base-agent stayed on base-dev:20 and the Agent image never got base:41's AgentHub Secrets hook.fritzlab/agent allowlists ci-bot, so base-agent's cascade to it works and keeps working unchanged.
Change: when the push is refused for branch protection, push the commit to
cascade/<name>-<tag>and open a pull request againstmainwith the same title. A re-run reuses the branch and treats the 409 for an existing pull request as success. Any other API answer fails the step as before. The script moves out ofaction.yamlintocascade.sh(same pattern as action/check-naming) so it can be tested.Tests
New
tests/run(CI:.gitea/workflows/test.yaml, as in check-naming) drivescascade.shagainst local bare repositories, with a pre-receive hook standing in for branch protection andtests/bin/curlfor the Gitea API. Run insidefritzlab/base-dev:20(the runner's toolchain):protected main gets a pull request,a re-run reuses the open pull request,a refused pull request fails the step)Rollout
Consumers pin
@v1, so this takes effect only when thev1tag is moved to the merge commit (git tag -f v1 <sha> && git push -f origin v1). No consumer workflow changes. The next cascade into a protected repository then opens a pull request that goes through normal review.The alternative is a forge setting, not code: allowlist ci-bot for direct pushes on runner, base-dev and base-agent the way fritzlab/agent and the playbooks
new_protectiondefault already do. That lets bumps land unreviewed; this PR keeps review.🤖 Generated with Claude Code
LGTM
Authored-By: Claude Code (Sonnet 5) noreply@anthropic.com
LGTM
Authored-By: Claude (Sonnet 5) noreply@anthropic.com