You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Quarantined suite fails on main: lib/cli-version-check.test.sh #18063
The suite lib/cli-version-check.test.sh failed on main outside the affected set of the
merges since the last green full run, so no merge caused it and it demotes
nothing. It is quarantined: it keeps running, and while this issue is open its
failures demote no unattended merge, for at most 7 days from when this
issue was filed (merge.quarantine-days); after that they demote again. Fix
the suite, then close this issue. To add anything, comment on this issue
rather than editing it: an edited issue stops excusing the suite.
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Blast radius: the lib/cli-version-check.test.sh suite and possibly the lib script it covers; read by CI and the post-merge quarantine logic.
Reversible: yes; revert the fix.
Open questions: none
Understood: the suite lib/cli-version-check.test.sh failed on main outside the affected set of recent merges, so it is quarantined for up to 7 days. It needs a fix, and the failing run log will show the cause. I found no open duplicate and no merged pull request that already fixes it.
Not admitted to the issue lane: an own-agent filing needs exactly one source: <producer> label to be admitted unattended, so a listed human decides it; no trusted-human acceptance criteria: a listed human must put the confirmed - [ ] criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).
Reason: security
melodic-automation-lanes commented on Nov 21, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: lib/cli-version-check.test.sh passes on main again, via a fix to the suite or to lib/cli-version-check.mjs once the failure cause is known.
What made the suite fail in run 44950479481? The log is not readable in this run, and the suite is a thin wrapper that runs node --test on cli-version-check.test.mjs, so the cause is not visible in the repository.
RECOMMENDED: Read the failing run log first. Then fix the test or lib/cli-version-check.mjs, or the suite's declared dependencies if it only failed outside its affected set. Basis: .base/lib/cli-version-check.test.sh:3
Is the failure deterministic or flaky, for example network, timing, or host git or CLI version dependence?
RECOMMENDED: Run the suite several times on a clean checkout of b789157. If it passes, make it hermetic, for example by stubbing CLI and network lookups. Basis: judgment
Should the criteria include a fix for the same code copied into plugins/context7, plugins/firecrawl and plugins/playwright (lib/cli-version-check.mjs)?
RECOMMENDED: No. Limit the work to lib/ unless the failure cause is in the shared logic that those copies also carry. Basis: judgment
Sources read
/home/runner/work/claude-code-plugins/claude-code-plugins/refine-data/context.json: issue body gives the failing run URL and main SHA, with no cause
lib/cli-version-check.test.sh:3: wrapper that runs node --test on cli-version-check.test.mjs
To answer, post a comment that starts with this line:
**Decision recorded.** <answer>
Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.
The owner confirmed this issue's text as his spec for PR #18075. He answered in session 5db14743 on 2026-11-22 at about 00:31Z. Asked: "Is #18063's text your spec for PR 18075?" verbatim: "Yes, it's my spec (Recommended)".
Activity
github-actions commentedon Nov 21, 2026
Size: Small
Complexity: Medium
Uncertainty: Knowable
Flags: none
Blocked by: none
Blast radius: the lib/cli-version-check.test.sh suite and possibly the lib script it covers; read by CI and the post-merge quarantine logic.
Reversible: yes; revert the fix.
Open questions: none
Understood: the suite lib/cli-version-check.test.sh failed on main outside the affected set of recent merges, so it is quarantined for up to 7 days. It needs a fix, and the failing run log will show the cause. I found no open duplicate and no merged pull request that already fixes it.
Automated triage. A maintainer reviews it.
github-actions commentedon Nov 21, 2026
The triage sweep dispatched intake triage for this issue (dispatch 1; 2 runs that reach intake, or 6 dispatches, hand it to a maintainer).
melodic-automation-lanes commentedon Nov 21, 2026
Not admitted to the issue lane: an own-agent filing needs exactly one
source: <producer>label to be admitted unattended, so a listed human decides it; no trusted-human acceptance criteria: a listed human must put the confirmed- [ ]criteria in the body or post them as their own comment, or, on an issue a listed human filed, intake's newest refinement comment must hold them unedited. Admission takes the issue once each of those is met, when intake triages it again (.github/actions/resolve-config/admission-rules.json).Reason:
securitymelodic-automation-lanes commentedon Nov 21, 2026
The latest triage verdict holds nothing: admission moved the issue to
needs-owner-decision; its comment says why.melodic-automation-lanes commentedon Nov 21, 2026
Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.
Intended outcome: lib/cli-version-check.test.sh passes on main again, via a fix to the suite or to lib/cli-version-check.mjs once the failure cause is known.
Related work
Open questions
RECOMMENDED: Read the failing run log first. Then fix the test or lib/cli-version-check.mjs, or the suite's declared dependencies if it only failed outside its affected set. Basis: .base/lib/cli-version-check.test.sh:3
RECOMMENDED: Run the suite several times on a clean checkout of b789157. If it passes, make it hermetic, for example by stubbing CLI and network lookups. Basis: judgment
RECOMMENDED: No. Limit the work to lib/ unless the failure cause is in the shared logic that those copies also carry. Basis: judgment
Sources read
To answer, post a comment that starts with this line:
Automated refinement by the lanes App. Answer with a comment whose first line is
**Decision recorded.**.kyle-sexton commentedon Nov 22, 2026
The owner confirmed this issue's text as his spec for PR #18075. He answered in session 5db14743 on 2026-11-22 at about 00:31Z. Asked: "Is #18063's text your spec for PR 18075?" verbatim: "Yes, it's my spec (Recommended)".
Record: https://github.com/melodic-software/architecture/blob/main/docs/owner-decisions.md?plain=1#L317