Combine the weekly dependency batch into one PR - #97
Merged
Conversation
The dotnet monorepo bump raises the global.json pin from 10.0.302 to 10.0.400. CLAUDE.md names that version too and says to keep the two in sync, so update it in the same change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LkE6H4p3B9aQcecFweu1Qi
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.
Rolls PRs #92, #93, #94 and #95 into one branch so this batch takes a single CI run instead of four. Each of those four already passed CI on its own; merging them one at a time would mean four more runs against
mainplus rebases asmainmoves under each one.The four touch disjoint files, so every commit cherry-picked with no conflicts and each is kept as its own commit.
What is in here
Microsoft.AspNetCore.OpenApi8.0.29 -> 8.0.30 (src/WebApp)pinia4.0.2 -> 4.0.3 (src/vue/package-lock.jsononly)global.json10.0.302 -> 10.0.400,Microsoft.AspNetCore.Components.WebAssembly*10.0.10 -> 10.0.11,System.CommandLine2.0.10 -> 2.0.11Microsoft.NET.Test.Sdk18.8.1 -> 18.9.0One extra commit that was not in any of the four:
CLAUDE.mdnames the SDK version alongsideglobal.jsonand says to keep the two in sync, so it moves to 10.0.400 as well.docker-build.shuses the floatingsdk:10.0tag and needs no change.Checked locally
dotnet test test/FactorioTools.Teston this branch: 4302 passed, 0 failed (3m57s), on SDK 10.0.400 with Test.Sdk 18.9.0.dotnet restoreresolves the new versions forWebApp,FactorioTools.CliandFactorioTools.Test.npm ciinsrc/vueinstalls pinia 4.0.3 and reports 0 vulnerabilities; the lockfile still satisfies the^4.0.2range inpackage.json.BrowserWasmandBlazorWebAppwere not built locally (thewasm-toolsworkload is not installed here); CI covers them.Note on the SDK floor
The
global.jsonbump is the only change with a cost beyond the version number. It is a floor, not an exact pin (rollForward: latestMajor), so anyone on an SDK older than 10.0.400 will now fail to build until they update. That is the normal effect of this Renovate rule, just worth naming.Follow-up
Close #92, #93, #94 and #95 in favour of this one once it merges. #96 (lock file maintenance) is left alone - it was not part of the request.
🤖 Generated with Claude Code
https://claude.ai/code/session_01LkE6H4p3B9aQcecFweu1Qi