chore(deps): take seven of the nine major updates - #123
Merged
Conversation
Dependabot grouped nine majors into one pull request and it failed on every platform. Two of them cannot land yet, and merging the group would have meant merging those with them. Taken: commander 15, which 7, @types/node 26, @semantic-release/changelog 7, @semantic-release/git 11, conventional-changelog-conventionalcommits 10, and lint-staged 17. Typecheck, lint, build and 879 tests pass. Held back: **typescript 7** — this is what broke CI. typescript-eslint 8.67 does not accept it as a peer, so `npm install` cannot resolve the tree at all. Nothing to work around; it lands when the eslint toolchain supports TS 7. **js-yaml 5** — this one is the reason not to merge a group blind. It installs cleanly and typechecks, and then fourteen tests fail: every GitHub Actions workflow real-case fixture stops detecting its rule, along with action-file discovery. On a scanner whose Layer 2 exists to read those workflows, that is the difference between reporting a finding and silently reporting nothing. Whatever changed in how it parses needs to be understood before it ships, not discovered later by a user who was told their repository was clean.
This was referenced Aug 25, 2026
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.
Supersedes #118, which failed on every platform because it grouped nine majors together and two of them cannot land.
Taken
commander15 ·which7 ·@types/node26 ·@semantic-release/changelog7 ·@semantic-release/git11 ·conventional-changelog-conventionalcommits10 ·lint-staged17Typecheck, lint, build and 879 tests pass locally.
Held back, with reasons
typescript7 — this is what broke #118's CI.typescript-eslint@8.67does not accept TS 7 as a peer, sonpm installcannot resolve the tree:Nothing to work around here; it lands when the eslint toolchain supports it.
js-yaml5 — the reason not to merge a grouped major PR on faith. It installs cleanly and typechecks, and then 14 tests fail: every GitHub Actions workflow real-case fixture (RC-01 through RC-11) stops detecting its rule, plus action-file discovery.On a scanner whose Layer 2 exists to read those workflows, that is the difference between reporting a finding and silently reporting nothing — a false negative on a security tool, which is the worst failure mode it has. What changed in its parsing needs to be understood before it ships, not discovered by a user who was told their repository was clean.
Worth splitting
js-yamlinto its own PR so the rest of the group isn't held behind it.