Skip to content

fix(ci): scope the picomatch audit exception to development dependencies - #129

Merged
chenanran555 merged 1 commit into
mainfrom
codex/audit-picomatch-exception
Nov 18, 2026
Merged

chenanran555 merged 1 commit into
mainfrom
codex/audit-picomatch-exception

Conversation

@chenanran555

Copy link
Copy Markdown
Contributor

Summary

Let PR #128 and other pull requests run the audit while picomatch awaits a patched release.

Behavior / risk

The affected copies in bun.lock are reachable through development tools. The production audit runs first with every advisory enabled. The full audit applies a temporary exception for one advisory and still blocks any other finding. Remove the exception once the lockfile contains no affected copies. GHSA-fc5q-39xc-vjpf

Validation

  • Bun 1.4.4 against the public npm registry. The unfiltered baseline reported the advisory. bun scripts/verify.ts full --step audit passed with this change.
  • bun test ./scripts/audit.test.ts ./scripts/verify.test.ts passed all 20 tests. Biome passed for both changed files.
  • Registry-backed workspace checks confirmed that the production audit still blocks this advisory in a transitive runtime dependency and that the full audit still blocks other advisories.

PR #128 can sync from main once this lands.

@chenanran555
chenanran555 merged commit 672f359 into main Nov 18, 2026
16 checks passed
@chenanran555
chenanran555 deleted the codex/audit-picomatch-exception branch November 18, 2026 07:40
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