Repository navigation
fix: release candidate v7.14.0 fails scenario callers #751
Description
What happened?
The release lane tried v7.14.0 at v7-next in the test repository, and a scenario failed. Nothing was tagged and v7 did not move.
callers: DiluxOne/diluxone-test's main still requires .github/workflows/org-pull-request.yml (aworkflowsrule of DiluxOne): its pull requests run the pipeline atv7, not v7-next;sync-repos.py rulesetsleaves it out once it has test-pull-request.yml (no run)play: the play job ended in skipped (https://github.com/DiluxOne/.github/actions/runs/43562914042)
The lane's run: https://github.com/DiluxOne/.github/actions/runs/43562914042
Steps to reproduce
Run the release lane (.github/workflows/release-lane.yml) on v7.14.0's candidate: it plays every scenario of tests/release/scenarios.yml in the test repository at v7-next (scripts/release-scenarios.py play).
Problem
The release candidate v7.14.0 fails the release scenarios callers, play, so the lane releases nothing and v7 stays where it is.
Scope
- The cause of each failing scenario above (
callers,play), in the engine or in the scenario's fixtures, fixed with a test that would have caught it.
Out of scope
- Changing the gates or what they check.
Acceptance criteria
- C1: Given v7.14.0's candidate with the fix, when the release lane plays
callers,playin the test repository, then each passes and the lane releases it.
Criticality
Critical
Activity
dilux-bot commentedon Nov 14, 2026
The issue's board
🤖 AI-generated · Claude Opus 5.5 (Anthropic)
soydiloreto commentedon Nov 14, 2026
Expected: #748's guard refuses to play while the test repository still gets the required workflow. It clears once diluxone-test#823 (its own pull-request caller) merges and
sync-repos.py rulesetsleaves it out; the next lane run plays.🤖 AI-assisted · Claude Opus 5.5 (Anthropic)
dilux-bot commentedon Nov 14, 2026
I tried to turn this report into a Python test and could not: No test written. The report describes a state outside this repository, not a code defect. The lane's guard
at_candidate(scripts/release-scenarios.py:1336) refuses to play while diluxone-test's main still has aworkflowsrule for org-pull-request.yml. It did that and returned thecallersfailure with the message the report quotes. Theplayskip follows from that failure. The maintainer's comment on the issue says the guard is working as intended and clears once diluxone-test#823 merges andsync-repos.py rulesetsdrops the rule. The script's own--testcases (around lines 2649-2667) already cover the guard both ways, so any Python test I wrote would pass. I could not run git here, so I did not read the last commit, #749.What would settle it: Either (a) a lane run made after diluxone-test#823 has merged and
sync-repos.py rulesetshas dropped the rule, wherecallersstill fails. Include the JSON fromrepos/DiluxOne/diluxone-test/rules/branches/mainso a test can use it. Or (b) a run whereplayis skipped althoughcallerspassed, with that run's results.🤖 AI reproduction · claude-sonnet-5-5 (Anthropic) · $0.19280969999999997