build(deps): hold the majors the planned refactor will handle - #88
Merged
Conversation
Nine pull requests were open across three branches for major upgrades that all need code changes: React 18 to 19, FluentValidation 11 to 12, Microsoft.Data.SqlClient 6 to 7, Swashbuckle 6 to 10, jsdom 25 to 30 and jest-dom 6 to 8. None is a security fix — dotnet list package --vulnerable is clean and there are no open Dependabot alerts. They belong to a planned refactor rather than to routine maintenance, and several of them belong to the same one: React 19 changes rendering and effect semantics while jsdom 30 and jest-dom 8 change what the test environment does underneath. Upgrading piecemeal means debugging three things at once. Ignored rather than closed each week, for the reason the licence holds were: a decision retaken every Monday is not a decision, it is a queue nobody reads — which is how the genuinely urgent update gets missed. Majors only, and named individually rather than blanket-ignored. Patches and minors still arrive, so a security fix inside the current major is not blocked, and any new major from a package not on this list still surfaces. Remove the entries as the refactor takes each one.
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.
Nine pull requests were open across three branches for major upgrades that all need code changes. They belong to the planned refactor, not to routine maintenance.
react,react-domjsdom@testing-library/jest-domFluentValidationSwashbuckle.AspNetCoreMicrosoft.Data.SqlClientNone is a security fix.
dotnet list package --vulnerableis clean and there are no open Dependabot alerts.Several belong to the same piece of work: React 19 changes rendering and effect semantics, while jsdom 30 and jest-dom 8 change what the test environment does underneath. Upgrading piecemeal means debugging three things at once.
Why ignore rather than keep closing
Same reason as the licence holds: a decision retaken every Monday is not a decision, it is a queue nobody reads — which is how the genuinely urgent update gets missed.
Majors only, named individually rather than blanket-ignored. Patches and minors still arrive, so a security fix inside the current major is not blocked, and a new major from any package not on the list still surfaces.
Remove the entries as the refactor takes each one.