chore(coil): Dependabot runs go green: vendored repos excluded, 38 advisories re-resolved - #155
Merged
Merged
Conversation
|
Warning Review limit reachedNext included review available in 35 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Repository: radroid/t3code/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
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 |
The security-update jobs GitHub ran carried an empty ignore list for both npm blocks, so the `.repos/**` wildcard-ignore block never reached them and every alert inside the vendored subtrees became a red run. Collapse to one root block and use `exclude-paths`, the documented lever for vendored code. Drop the uuid and image-size ignores (no alerts in any state) and name decode-uri-component instead, whose fix needs an ESM-only query-string 8 that would patch react-navigation. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…ides Every open root alert is transitive, and Dependabot can only bump direct dependencies, so each one ends in security_update_not_possible and a red run. Re-resolve them the way the fork always has: overrides scoped to the major already in the tree. @xmldom/xmldom 0.8.13 -> 0.8.15, 0.9.10 -> 0.9.12 baseline-browser-mapping 2.10.33 -> 2.11.25 browserslist 4.28.2 -> 4.29.0 fast-uri 3.1.5 -> 3.1.8 hono 4.13.0 -> 4.13.8 qs 6.15.3 -> 6.16.0 xml2js 0.4.23 -> 0.6.2 (parent-scoped to dbus-next; the tree already carried 0.6 for expo) valibot: optional peer of drizzle-orm that nothing imports; with the override its spec has no provider, so it simply leaves the lock instead of pinning 1.2.0. decode-uri-component stays open on purpose (needs the ESM-only query-string 8). Verified: pnpm install --frozen-lockfile, tsc in apps/server and infra/relay, no vulnerable version left in pnpm-lock.yaml. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
radroid
force-pushed
the
coil/dependabot-advisories
branch
from
September 20, 2026 12:02
ef65ae8 to
8d24a61
Compare
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.
Every Dependabot security-update run on this fork has been red. Two causes, one concern:
The config never reached the jobs. The security-update jobs GitHub actually ran carried
"ignore-conditions": []for both npm blocks, so the.repos/**wildcard-ignore block never applied, and every alert inside the vendored subtrees became a red run (Dependabot cannot update them anyway: alchemy-effect's manifest references a git submodule that is not in the subtree copy). The config is now one root block withexclude-paths: [".repos/**"], the documented lever for vendored code. Staleuuidandimage-sizeignores are dropped (no alerts in any state);decode-uri-componentis named instead because its fix needs the ESM-only query-string 8, which would patch react-navigation.Every root alert is transitive. Dependabot only bumps direct dependencies, so each of the 38 open root alerts ended in
security_update_not_possible. They are re-resolved through major-scoped overrides inpnpm-workspace.yaml, the fork's standing playbook:xml2js is the one parent-scoped entry: dbus-next's
^0.4range has no patched release, and the tree already carried xml2js 0.6 for expo-splash-screen. dbus-next is only loaded on Linux desktop; not exercised on this machine. valibot was an optional peer of drizzle-orm that nothing in the repo imports; with the override its spec has no provider, so it leaves the lock rather than pinning a vulnerable version.Verified locally:
pnpm install --frozen-lockfilesucceeds,tsc --noEmitpasses inapps/serverandinfra/relay, and no vulnerable version remains inpnpm-lock.yaml. The devalue alert on.repos/alchemy-effectwas dismissed as not used.Written by Claude Fable 5.1 via Claude Code.
🤖 Generated with Claude Code