fix(dependabot): validate exclusions and restore update jobs - #563
Conversation
|
ty-everett
left a comment
There was a problem hiding this comment.
Maintainer critical review of exact head 76e53be: replaces only the schema-invalid ancestor exclusions with recursive filename globs, preserving root and standalone npm coverage. The dependency-free guard is linear string parsing after correcting the new Sonar performance finding. Regression evidence and all required local checks passed, followed by successful exact-head CI, Conformance, CodeQL and zero-new-Sonar checks. No open CodeQL merge-ref alert or review thread remains. Approved for maintainer integration; the live Dependabot configuration and update jobs will be verified immediately after merge. No dependency versions, credentials, permissions or quality thresholds change.



Program and scope
GitHub rejected the parent-relative
exclude-pathsadded in #562 and disabled all Dependabot update jobs. Replace them with recursive filename globs that match the same ancestor pnpm support files at both infrastructure directory depths. Add an early, dependency-free regression check for GitHub's forbidden..patterns. Advances #402.Impact
Root pnpm scanning and all eight infrastructure npm manifests/lockfiles remain monitored. Monthly grouping, immediate security updates, first-party release ownership, and workflow permissions are unchanged. No package version change is needed.
Verification
pnpm health:check,pnpm lint,pnpm format:check,pnpm build, and post-buildpnpm typecheckpassed. A fresh checkout requires its built declarations before typechecking documentation consumers.File.fnmatch?flags match all four ancestor support-file paths, without matchingpackage.jsonorpackage-lock.json.Security and dependencies
Dependency evidence
..; the existing updater workaround must use accepted syntax.Release and operations