Skip to content

Update renovate.json - #198

Merged
dunningdan merged 1 commit into
mainfrom
dunningdan-patch-1
Nov 13, 2024
Merged

Update renovate.json#198
dunningdan merged 1 commit into
mainfrom
dunningdan-patch-1

Conversation

@dunningdan

Copy link
Copy Markdown
Member

No description provided.

@dunningdan
dunningdan requested a review from drdavella November 13, 2024 19:31
@dunningdan
dunningdan merged commit ef7f971 into main Nov 13, 2024
@dunningdan
dunningdan deleted the dunningdan-patch-1 branch November 13, 2024 19:32
dunningdan added a commit that referenced this pull request Sep 7, 2026
#302 cleared 42 of 51 Dependabot alerts by refreshing yarn.lock, but 9
survive because re-resolution provably cannot reach them - their parents
either pin an exact version or cap below the patched release:

  minimatch             parent pins 9.0.3 exactly      -> 9.0.9
  yaml                  parent pins 2.8.1 exactly      -> 2.9.0
  serialize-javascript  parent caps at ^6.0.0          -> 7.1.1
  uuid                  parent caps at ^8.3.2          -> 11.1.1
  qs                    parent caps at ~6.15.1         -> 6.16.0

yarn resolutions are the only lever here, following the existing `got`
entry. This clears 9 of the 11 currently open alerts.

qs is the newest of these: GHSA for it was published Sep 2 and GitHub
raised alerts #197/#198 three minutes after #302 merged, against the
freshly refreshed lockfile. `~6.15.1` excludes 6.16.0, so no future
lockFileMaintenance pass would have fixed it either.

Remaining open after this: #186/#187 image-size, which has no patched
version published upstream. Reached via @docusaurus/mdx-loader at build
time only; tracked for risk acceptance rather than code change.

Verified on Node 24.20.0: yarn build passes (59 documents) and the dev
server serves HTTP 200, which exercises sockjs -> uuid@11, the one bump
here that crosses major versions and that a production build would not
otherwise cover.

Also refreshes the lockFileMaintenance description - it still told the
reader to restore a weekly schedule, which is no longer the intent. No
behavior change; schedule stays "at any time".

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.

2 participants