Skip to content

Update to dotnet10 - #652

Merged
donaldgray merged 7 commits into
developfrom
feature/dotnet10
Aug 24, 2026
Merged

Update to dotnet10#652
donaldgray merged 7 commits into
developfrom
feature/dotnet10

Conversation

@donaldgray

@donaldgray donaldgray commented Aug 19, 2026

Copy link
Copy Markdown
Member

What does this change?

Upgrade to dotnet10, resolves #647

  • Bump all Docker images and csproj etc
  • Bump all nuget packages with exception of fluentAssertion due to licensing change
    • AWS sdk update from v3->v4 returns null now, rather than empty collections so added handling for those.
  • Remove a couple of warnings, mostly nullability for Hierarchy and a few incorrect XML comments (e.g. referencing JSType.Error.Title, rather than our own Error.Title).
  • Remove unused classes/methods (PresentationController.HandleDelete() and DeleteEntityResult)
  • Introduced some primary ctors and extension blocks
  • Tidy up cleanupHandler to tear down customer 1 resources, no tests affected but without there was a sporadic failure issue when running integration tests.
  • Tweak LocalStackFixture health check, without this the image could report as ready before some of the svcs (e.g. s3) was ready

Configuration Changes

Note

This PR introduces configuration changes.

Service AppSetting Required? Description Default
API MEDIATR_LICENSE_KEY or LUCKYPENNY_LICENSE_KEY Y License key for Mediatr null

Mediatr is now on 13+, which requires a license. To avoid baking into container image we can provide via envvars, see https://github.com/LuckyPennySoftware/MediatR#setting-the-license-key for details.

@donaldgray
donaldgray requested a review from a team as a code owner August 19, 2026 14:17
Minimal changes, same functionality.
* Remove unused method/classes
* Remove unused using
* Resolve some unused usings
* Introduce some extension blocks to tidy helper classes
* Remove obsolete props
These are both identical images but the former is self documenting and
consistent with other projects in org
* Set checksum override for SQS clients using localstack. I don't think
this is ever actually exercised but would cause issues if project was
run against localstack locally.
* Change nullability of s3 headers in our mapped object to map
downstream
* Remove now defunct xml header
Change in behaviour for 3->4, it will now return null, whereas
previously it would return a empty
@donaldgray
donaldgray merged commit 94713c7 into develop Aug 24, 2026
4 checks passed
@donaldgray
donaldgray deleted the feature/dotnet10 branch August 24, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Dotnet 10

2 participants