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
As a SkillSpector user on current OpenCode, I want the opencode_cli deny-all policy re-verified against each new CLI release so the version gate keeps me safe without stranding me on an old binary.
The gap
The merged provider fails closed on anything but exactly 1.18.30. OpenCode 1.18.31 is out, so latest-version users get a refusal instead of scans — correct behavior, now needing re-verification.
What I am asking for
Please consider a re-verification bump: confirm identical flags/behavior, move the pin and all version references, and prove it with the existing gates plus a live self-scan. Done when the provider runs green on 1.18.31 with no policy changes.
This could be achieved by:
Bumping _OPENCODE_SUPPORTED_VERSION and all version references (comments, fixtures, README pin note, DEVELOPMENT)
Fixing any test that hardcoded either side of the pin boundary
Re-running provider suites, lint, and a live self-scan on the new release
Activity