fix(deps): clear 2026-09-29 advisories and close a CI path-filter blind spot - #284
Merged
Merged
Conversation
…nd spot `bun audit` now reports zero findings at every severity in both workspaces. Two advisories published 2026-09-29 tripped the `--audit-level=high` gate: brace-expansion (high, DoS via uncontrolled recursion) and fast-uri. Also cleared the moderate set that matters most for a proxy -- ip-address (SSRF/trust-boundary), hono (memory exhaustion, query-parser differentials, JSX escaping) and dompurify (DOM XSS). All are `overrides` bumps, so no direct dependency range moves. Separately, Cross-platform CI now triggers on `.github/workflows/**` instead of an enumerated file list. That list had drifted and omitted container.yml and deploy-docs.yml, so a PR touching only one of them ran no tests at all -- which is how the three merged Dependabot pin bumps landed a commit that broke tests/ci-workflows.test.ts while every check reported clean. The action pins in that test are updated to the new SHAs, each verified against its upstream release tag first. Co-Authored-By: Codex <noreply@openai.com>
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: GroepOnline/opencodex/.coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Advisories
Two advisories published 2026-09-29 tripped the
bun audit --audit-level=highgate on
main.bun auditnow reports zero findings at every severity inboth workspaces.
All are
overridesentries, so no direct dependency range moves and thelockfile diff is limited to those packages.
CI path-filter blind spot
tests/ci-workflows.test.tspins the action SHAs ofcontainer.ymlanddeploy-docs.yml. The three Dependabot PRs merged today changed exactly thoseSHAs — and the suite went red.
It stayed red on
mainsilently becauseci.ymlgates on apaths:list thatenumerates workflow files individually. That list had drifted and omitted
container.ymlanddeploy-docs.yml, so a PR touching only one of them ranno tests at all. Every check on all three PRs reported clean.
The trigger is now
.github/workflows/**, which cannot drift the same way.Verification
bun audit— clean at every severity, root andguibun run typecheck— cleanbun run privacy:scan— passedtests/ci-workflows.test.ts— 90 pass / 0 failscripts/ci-test-shard.ts— 4 failures, byte-identical to thesame run on clean
main(CLI help ×2, service diagnostics, codex-runtime);none introduced here
Note
The 4 remaining failures are pre-existing on
mainand reproduce on a cleancheckout. They are unrelated to this change.