chore(examples): migrate examples and docs to .NET 10 - #1267
Open
nicolastarzia wants to merge 1 commit into
Open
chore(examples): migrate examples and docs to .NET 10#1267nicolastarzia wants to merge 1 commit into
nicolastarzia wants to merge 1 commit into
Conversation
Migrate all example projects from .NET 8 (and lingering .NET 6 runtimes) to .NET 10, and add a v4 migration guide. - Bump all example .csproj TargetFramework net8.0 -> net10.0 - Update SAM templates Runtime dotnet6/dotnet8 -> dotnet10 - Update aws-lambda-tools-defaults.json function-runtime -> dotnet10 - Update container examples: Dockerfile base images repinned to real .NET 10 digests (MCR sdk 10.0, ECR Public lambda/dotnet 10.x, both multi-arch) and publish path net6.0 -> net10.0; DockerTag -> dotnet10.0-v1 - Fix Kafka Protobuf OutputDir net8.0 -> net10.0 - Update example READMEs (.NET 8.0 -> .NET 10.0, dotnet8 -> dotnet10) - Update root README dotnet badge and managed runtime text - Add docs/migration-guide-v4.md Verified: example test suites pass on net10.0 (26 tests). Idempotency integration test requires Docker (Testcontainers) and was not run locally.
boring-cyborg
Bot
added
the
documentation
|
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
powertools-for-aws-oss-automation
Bot
added
the
size/L
|
hjgraca
requested changes
Sep 7, 2026
| --- | ||
| title: Migration Guide v4 | ||
| slug: migration-guide-v4 | ||
| description: Migration guide to upgrade to v4 (.NET 10) |
Contributor
There was a problem hiding this comment.
This is not a major version release
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
2 participants
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.
Issue number: #1268
Closes #1268
Summary
Changes
Migrates all example projects and documentation from .NET 8 (with some lingering .NET 6 runtimes) to .NET 10, and adds a v4 migration guide. This PR intentionally does not touch the production libraries under
libraries/src/— those already multi-targetnet8.0;net10.0..csprojnet8.0→net10.0Runtimedotnet6/dotnet8→dotnet10aws-lambda-tools-defaults.jsonfunction-runtime→dotnet10dotnet/sdk:10.0and ECR Publiclambda/dotnet:10.x(both multi-arch amd64+arm64), resolved directly from the registriesnet6.0→net10.0DockerTagdotnet6.0-v1→dotnet10.0-v1OutputDirnet8.0→net10.0.NET 8.0→.NET 10.0,dotnet8→dotnet10), root README badge + managed-runtime text, and a newdocs/migration-guide-v4.mdSeveral SAM templates were previously on
dotnet6while their.csprojwere alreadynet8.0(pre-existing inconsistency), now aligned ondotnet10.User experience
Before: copying an example gives a project targeting
net8.0(or a SAM template still on thedotnet6/dotnet8managed runtime), pointed at a runtime about to reach end of support.After: examples target
net10.0and deploy on thedotnet10managed runtime out of the box, aligned with the current LTS runtime and with the libraries that already support net10.0.Checklist
Please leave checklist items unchecked if they do not apply to your change.
Testing
net10.0— 26 tests, 0 failures: Logging (1), Metrics (1), Tracing (1), BatchProcessing (13), Parameters (6), ServerlessApi (1), AOT Logging/Metrics/Tracing (1 each)Known limitation: the Idempotency example test is an integration test that spins up DynamoDB Local via Testcontainers (Docker). It could not be executed locally (no Docker daemon). The code compiles cleanly on
net10.0; only the test infrastructure was unavailable — please validate in CI.Is this a breaking change?
No. This changes only the example projects and documentation; no production library code is modified.
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.