Repository navigation
Update all dependencies and retarget to .NET 11 - #27
Merged
Merged
Conversation
- Retarget the solution, Dockerfile images and .NET example to .NET 11 (Lambda bootstrap/test handler stay on net10.0 to match the dotnet10 runtime). - Bump NuGet packages (ASP.NET Core 11, Aspire 13.6.5, MessagePack 3, MinVer 8, xunit.v3 4.0.3, bunit, AWSSDK, Testcontainers, Atoll). - Add Smithy RPC v2 CBOR support for Cloud Map; AWSSDK.ServiceDiscovery 4.0.102+ switched protocols. - Prune vulnerable System.Formats.Cbor 9.0.5 via the shared framework. - Work around ASP.NET 11 analyzer issues in the Resources page and UI tests. - Update Go, Python (universal hashed lock), Java (25, Testcontainers 2, JUnit 6) and TypeScript examples. - Move CI to latest action majors, .NET 10+11, Java 25, Node 24, Python 3.14. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.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.
Brings every dependency up to date: NuGet packages, the .NET target, the Testcontainers examples and the CI toolchains. Restore was also failing NuGet audit (Aspire 13.6.4 and a transitive
System.Formats.Cbor9.0.5), and the floatingAWSSDK.*4.x versions had silently broken Cloud Map support.Changes
.NET
sdk/runtime-deps:11.0-alpine) and the .NET example tonet11.0.MicroStack.LambdaBootstrapandSimpleHandlerdeliberately stay onnet10.0: they model the AWSdotnet10Lambda runtime andLambdaWorkerhardcodes that TFM.Cloud Map: Smithy RPC v2 CBOR
POST /service/Route53AutoNaming_v20170314/operation/<Op>with a CBOR body. The emulator rejected these with "Invalid JSON", which broke all 16ServiceDiscoveryTests.mainwill hit the same failure on its next restore.Internal/SmithyRpcV2Cbor.cs, a reusable adapter that:X-Amz-Targetfrom the path;servicediscoveryexplicitly instead of relying on the credential scope.Security
MicroStack.Testsgets aFrameworkReferencetoMicrosoft.AspNetCore.App, so NuGet prunes the vulnerableSystem.Formats.Cbor9.0.5 thatAWSSDK.Extensions.CborProtocolpulls in. The latest CborProtocol still depends on 9.0.5.ASP.NET 11 analyzer workarounds
Resources.razor: replaced an@forloop withforeachover.Index()to avoid an NRE in the new for-loop closure analyzer (AD0001).Resources.razor.cs: JS interop calls now catchJSException.IJSRuntime.Examples
requirements.lockis now generated withuv pip compile --universal --generate-hashes, so it installs with--require-hasheson Python 3.10-3.14 and on every OS.testcontainers-junit-jupiter), JUnit 6.1.3, latest compiler and surefire plugins.CI
dotnet-quality: preview.Docs: updated the .NET and Java version references.
Review notes
npm auditstill reports 6 moderate issues, all via testcontainers -> archiver. They can only be fixed upstream.Verification (local)
dotnet build MicroStack.slnx -c Releaseand the Docs build are clean apart from ASPIRE010.dotnet list package --vulnerablereports nothing;--outdatedfinds no updates in any project.docker build, the container contract tests, all five Testcontainers examples and the container smoke test pass against the new image.