Skip to content

fix(opencode-plugin): clear the high advisory blocking the release gate - #17

Merged
phall1 merged 1 commit into
mainfrom
fix/plugin-audit-gate
Sep 9, 2026
Merged

fix(opencode-plugin): clear the high advisory blocking the release gate#17
phall1 merged 1 commit into
mainfrom
fix/plugin-audit-gate

Conversation

@phall1

@phall1 phall1 commented Sep 9, 2026

Copy link
Copy Markdown
Owner

opencode-plugin-v0.2.2 was tagged but never published. The release
workflow runs npm run gates, which ends in npm audit --audit-level=high, and
GHSA-2883-xcg3-v3hh (js-yaml, high) landed after 0.2.1 shipped. The gate failed
before the publish job, so the tag points at a version npm does not have.

The gate did its job — nothing reached the registry.

js-yaml reaches this package only through eslint → @eslint/eslintrc, so it is
dev-only and never shipped. The gate is deliberately blind to that, and that is
the right default: a lockfile carrying a known high advisory is worth failing on
even when the published artifact does not contain it.

npm audit fix resolves it non-breaking, 4.3.1 → 4.3.2. The two remaining
advisories are moderate (vitest) and below the gate's threshold; clearing them
requires vitest 5, a breaking upgrade that does not belong in a release hotfix.

pi-extension and claude-plugin do not resolve js-yaml at all, so neither is
affected.

Rather than retag v0.2.2 — a destructive rewrite of a published ref — this
lands as a normal fix so release-please cuts 0.2.3 and the OpenCode V2
plugin fix from #16 finally reaches npm.

Gates pass end to end locally: check, 29 tests, pack, audit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01HvvVk5xnS9hRBL9u1WcP6p

The release workflow runs `npm run gates`, which ends in
`npm audit --audit-level=high`. GHSA-2883-xcg3-v3hh (js-yaml, high) was
published after 0.2.1 shipped, so the v0.2.2 publish failed on the gate before
reaching the registry -- nothing was published, and the tag now points at a
version npm does not have.

js-yaml reaches this package only through eslint -> @eslint/eslintrc, so it is
dev-only and never shipped, but the gate is deliberately blind to that and it
is the right default: a lockfile carrying a known high advisory is worth
failing on even when the artifact does not contain it.

`npm audit fix` resolves it non-breaking, 4.3.1 -> 4.3.2. The two remaining
advisories are moderate (vitest) and below the gate's threshold; clearing them
needs vitest 5, which is a breaking upgrade and does not belong in a release
hotfix.

pi-extension and claude-plugin do not resolve js-yaml at all, so neither is
affected.

Gates pass end to end: check, 29 tests, pack, audit.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HvvVk5xnS9hRBL9u1WcP6p
@phall1
phall1 merged commit f103772 into main Sep 9, 2026
3 checks passed
@phall1
phall1 deleted the fix/plugin-audit-gate branch September 9, 2026 09:44
@phall1 phall1 mentioned this pull request Sep 9, 2026
phall1 added a commit that referenced this pull request Sep 9, 2026
🤖 I have created a release *beep* *boop*
---


<details><summary>opencode-plugin: 0.2.3</summary>

##
[0.2.3](opencode-plugin-v0.2.2...opencode-plugin-v0.2.3)
(2026-09-09)


### Bug Fixes

* **opencode-plugin:** clear the high advisory blocking the release gate
([#17](#17))
([f103772](f103772))
</details>

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant