chore(deps): re-resolve orphaned security alerts within existing ranges - #155
Merged
Merged
Conversation
Dependabot files one PR per package name, not per alert. Where a package is vulnerable on two major lines it fixes one and leaves the other open indefinitely: #146 fixed form-data 2.x while 4.x stayed at 4.0.5, #133 fixed js-yaml 3.x while 4.x stayed at 4.3.0, #142 fixed brace-expansion 1.x while 2.x and 5.x stayed behind. Every one of these is reachable from the ranges already declared, so `yarn up -R` lifts them without touching any manifest: brace-expansion ^2.0.1 2.0.2 -> 2.1.4 (#87) brace-expansion ^5.0.2 5.0.4 -> 5.0.9 (#85) form-data ^4.0.0 4.0.5 -> 4.0.6 (#67) js-yaml ^4.1.0 4.3.0 -> 4.3.1 (#122) picomatch ^2.0.4 2.3.1 -> 2.3.2 (#16) picomatch ^4.0.2 4.0.3 -> 4.0.5 (#15) The mime-types descriptor list loses "^2.1.12" because form-data 4.0.6 raised its own floor to ^2.1.35; the resolved mime-types version is unchanged. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Closes Dependabot alerts #15, #16, #67, #85, #87, #122.
Why these were stuck
Dependabot files one PR per package name, not per alert. When a package is vulnerable on two major lines it fixes one and leaves the other open indefinitely:
js-yaml #122 has sat open since 07 Aug while ~15 other Dependabot PRs went out, so these will not resolve themselves.
What this does
Every one of these is reachable from ranges already declared, so
yarn up -Rlifts them without touching any manifest:brace-expansion^2.0.1, ^2.0.2brace-expansion^5.0.2form-data^4.0.0, ^4.0.5js-yaml^4.1.0, ^4.2.0picomatch^2.0.4 …picomatch^4.0.2, ^4.0.3Lockfile-only: 21 insertions, 21 deletions, no packages added or removed, no majors crossed. brace-expansion 1.x and js-yaml 3.x are deliberately absent — #142 and #133 already put them at their highest in-range versions.
One incidental line
The descriptor list shrinks because form-data 4.0.6 raised its own floor from
mime-types: ^2.1.12to^2.1.35. The resolved mime-types version is unchanged at 2.1.35 — cosmetic, nothing moved.Verification
picomatchandbrace-expansionare the glob engines under jest, eslint and webpack, so this got the full pipeline rather than a lockfile glance:yarn install --immutableyarn typecheckyarn buildyarn lintyarn testyarn format:checkyarn workspace app buildThe last row matters: CI's
yarn buildis scoped to--include '@rwdocs/*', so it never bundles the frontend app. Ran explicitly.Notes
@backstage/clitooling,supertest, eslint/jest globbing), so this is hygiene rather than urgent — it just clears alerts that would otherwise never close.package.jsonchanges, noresolutionsoverrides.🤖 Generated with Claude Code