Repository navigation
Harden dependency update policy - #3
Merged
Merged
Conversation
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.
What changed\n\n- group only minor and patch development dependency updates\n- keep TypeScript and Node type-definition major upgrades under manual review\n- explicitly load Node types in the shared TypeScript configuration\n\n## Why\n\nDependabot grouped TypeScript 7 and @types/node 26 into one major update. TypeScript then stopped resolving the implicit Node globals used by the CLI, causing every CI matrix job to fail.\n\n## Impact\n\nRoutine dependency maintenance remains automated, including security updates. Toolchain baseline changes become deliberate, isolated upgrades.\n\n## Validation\n\n- pnpm check (22 tests)\n- pnpm build\n- Dependabot YAML parsed successfully