[FEATURE] Upgrade to .NET 10 LTS

[nanotaboada]

Problem

.NET 8 LTS support ends in November 2026 (~9 months remaining). The project needs to migrate to .NET 10 LTS to ensure continued support, security updates, and access to the latest performance improvements and features for the next 2.7+ years.

Proposed Solution

Upgrade the entire solution from .NET 8 to .NET 10 LTS, leveraging new runtime performance improvements, C# 14 language features, and enhanced SDK capabilities while maintaining backward compatibility and existing functionality.

Suggested Approach

1. Update Target Framework

   • Modify all .csproj files to target net10.0
   • Update global.json to specify .NET 10 SDK version

2. Update Dependencies

   • Upgrade all NuGet packages to .NET 10 compatible versions
   • Update ASP.NET Core packages to 10.0.x
   • Update Entity Framework Core (if used) to 10.0.x
   • Review and update test framework packages

3. Docker Configuration

   • Update Dockerfile base images to .NET 10 SDK and runtime
   • Update compose.yaml if it references specific .NET versions

4. CI/CD Pipeline Updates

   • Update azure-pipelines.yml to use .NET 10 SDK
   • Update GitHub Actions workflows (if any) to use .NET 10

5. Code Modernization (Optional)

   • Leverage C# 14 features where beneficial (field-backed properties, extension blocks)
   • Review and apply new performance optimizations
   • Consider WebSocketStream for WebSocket implementations
   • Evaluate post-quantum cryptography APIs if applicable

6. Testing & Validation

   • Run existing test suite to ensure compatibility
   • Perform regression testing
   • Update unit tests if behavior changes are detected
   • Load/performance testing to validate improvements

Acceptance Criteria

• All projects target net10.0 framework
• All NuGet packages updated to .NET 10 compatible versions
• Dockerfile uses .NET 10 SDK and runtime images
• CI/CD pipelines successfully build with .NET 10
• All existing unit tests pass
• All integration tests pass
• Application runs successfully in local development environment
• Docker container builds and runs successfully
• No breaking changes introduced to public APIs
• README.md updated to reflect .NET 10 requirement
• CHANGELOG.md updated with upgrade notes

References

• .NET Support Policy
• What's new in .NET 10
• What's new in ASP.NET Core 10
• What's new in C# 14
• Migrate from .NET 8 to .NET 10

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#126 - chore(deps): bump the efcore group with 4 updates [merged]
#127 - chore(deps): bump Microsoft.VisualStudio.Web.CodeGeneration.Design from 8.0.3 to 8.0.4 [merged]
#130 - chore(deps): bump Microsoft.NET.Test.Sdk from 17.10.0 to 17.11.0 [merged]
#316 - ci: migrate Azure Pipeline from Windows/MSBuild to Linux/.NET CLI [merged]

---

🧪 Issue enrichment is currently in open beta.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[coderabbitai]

Coding Plan

Approach

• Update target framework and create global.json to establish .NET 10 as the project SDK baseline
• Upgrade Microsoft packages (ASP.NET Core, EF Core, Test SDK) to 10.0.x versions while retaining compatible third-party packages at current versions
• Update all build infrastructure (Docker, Azure Pipelines, GitHub Actions) consistently to use .NET 10
• Cut the first release (v1.0.0-azteca) as the .NET 10 upgrade represents a significant framework change that justifies an official release milestone

Observations

The solution consists of two .csproj files: a main ASP.NET Core Web API project (src/Dotnet.Samples.AspNetCore.WebApi/) and an xUnit test project (test/Dotnet.Samples.AspNetCore.WebApi.Tests/), both currently targeting .NET 8.0. The application uses modern patterns including minimal hosting model with WebApplicationBuilder, primary constructors (C# 12), TypedResults API, Entity Framework Core with SQLite, and comprehensive dependency injection. Build infrastructure includes a multi-stage Dockerfile using .NET 8 images, Azure Pipelines (azure-pipelines.yml), and two GitHub Actions workflows (dotnet-ci.yml, dotnet-cd.yml). Package lock files are enabled for reproducible builds. No global.json currently exists in the repository. The project uses semantic versioning with stadium-themed codenames (e.g., v1.0.0-azteca) and has no releases yet—only an [Unreleased] section in CHANGELOG.md.

Assumptions

Assumption 1: AutoMapper Version Constraint Strategy

Options Considered:

1. Keep the existing version constraint and only update if compatibility issues arise
2. Remove the constraint and update to the latest AutoMapper version

Chosen Option: 1

Rationale: Maintain the existing constraint as it represents an intentional stability decision; AutoMapper 14.x is compatible with .NET 10 and the constraint can be revisited if specific issues emerge.

Assumption 2: Release Strategy for .NET 10 Upgrade

Options Considered:

1. Cut a new release (v1.0.0-azteca) to mark this as the first official release with .NET 10 LTS
2. Keep changes in the [Unreleased] section and defer release to a later milestone

Chosen Option: 1

Rationale: A major framework upgrade from .NET 8 to .NET 10 LTS justifies cutting the first release. This is a foundational change that alters runtime requirements (users need .NET 10), updates all Docker images, and represents a stable baseline. Since no releases exist yet, version 1.0.0-azteca (using the first stadium in the alphabetical list) is appropriate as the initial release.

💡 User Tips

Regenerate the plan with different choices with @coderabbitai <feedback>.

Implementation Steps

Phase 1: Project Configuration and Dependencies

Update all project files to target .NET 10, establish SDK version pinning via global.json, and upgrade all NuGet packages to .NET 10 compatible versions.

Task 1: Update Target Framework in Project Files

Change the target framework from net8.0 to net10.0 in both project files.

• Update src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj to change <TargetFramework>net8.0</TargetFramework> to <TargetFramework>net10.0</TargetFramework>
• Update test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj with the same target framework change
• No other property changes required as ImplicitUsings and Nullable settings remain valid

Task 2: Create global.json for SDK Version Pinning

Create a new global.json file in the repository root to pin the .NET 10 SDK version and ensure consistent builds across environments.

• Create global.json in the repository root directory
• Specify SDK version using 10.0.100 or latest stable .NET 10 SDK version
• Include rollForward policy set to latestFeature to allow patch updates while maintaining major version stability
• This addresses the current absence of SDK version pinning noted in the exploration

Task 3: Update NuGet Package References in Main Project

Upgrade all NuGet packages in the main application project to .NET 10 compatible versions.

• Update src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj with the following package updates:
• Change Microsoft.AspNetCore.OpenApi from 8.0.23 to 10.0.x (align with target framework)
• Change Microsoft.EntityFrameworkCore.Sqlite from 9.0.12 to 10.0.x
• Change Microsoft.EntityFrameworkCore.Design from 9.0.12 to 10.0.x
• Update Microsoft.VisualStudio.Web.CodeGeneration.Design to 10.0.x compatible version
• Verify Microsoft.Extensions.Configuration.Json 10.0.x compatibility (already at 10.0.2)
• Retain AutoMapper constraint [14.0.0,15.0.0) unless build issues occur
• Keep Serilog, FluentValidation, and Swashbuckle packages at current versions (already .NET 10 compatible)

Task 4: Update NuGet Package References in Test Project

Upgrade test framework packages to .NET 10 compatible versions.

• Update test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj with package updates
• Update Microsoft.NET.Test.Sdk from 18.0.1 to latest .NET 10 compatible version
• Verify xunit, xunit.runner.visualstudio, Moq, FluentAssertions, and coverlet.collector compatibility (current versions should work)
• Update any packages that show compatibility warnings during restore

Task 5: Regenerate Package Lock Files

Delete and regenerate package lock files to reflect updated dependency graph.

• Delete src/Dotnet.Samples.AspNetCore.WebApi/packages.lock.json
• Delete test/Dotnet.Samples.AspNetCore.WebApi.Tests/packages.lock.json
• Run dotnet restore --force-evaluate to regenerate lock files with .NET 10 compatible package versions
• Commit the regenerated lock files to ensure reproducible builds

🤖 Prompt for AI agents

This phase updates project configuration and dependencies to target .NET 10,
including creating SDK version pinning and upgrading all NuGet packages.

**Target Framework Updates:**
- In
`src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj`,
change `<TargetFramework>net8.0</TargetFramework>` to
`<TargetFramework>net10.0</TargetFramework>`
- In
`test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj`,
change `<TargetFramework>net8.0</TargetFramework>` to
`<TargetFramework>net10.0</TargetFramework>`
- ImplicitUsings and Nullable settings should remain unchanged

**SDK Version Pinning:**
- Create `global.json` in repository root
- Set SDK version to `10.0.100` (or latest stable .NET 10 SDK version)
- Set `rollForward` policy to `latestFeature` for patch updates while
maintaining major version stability

**NuGet Package Updates - Main Project
(`src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj`):**
- Update `Microsoft.AspNetCore.OpenApi` from 8.0.23 to 10.0.x
- Update `Microsoft.EntityFrameworkCore.Sqlite` from 9.0.12 to 10.0.x
- Update `Microsoft.EntityFrameworkCore.Design` from 9.0.12 to 10.0.x
- Update `Microsoft.VisualStudio.Web.CodeGeneration.Design` to 10.0.x compatible
version
- Verify `Microsoft.Extensions.Configuration.Json` 10.0.x compatibility
(currently at 10.0.2)
- Keep AutoMapper constraint `[14.0.0,15.0.0)` unchanged
- Keep Serilog, FluentValidation, and Swashbuckle packages at current versions

**NuGet Package Updates - Test Project
(`test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj`):**
- Update `Microsoft.NET.Test.Sdk` from 18.0.1 to latest .NET 10 compatible
version
- Verify compatibility of xunit, xunit.runner.visualstudio, Moq,
FluentAssertions, and coverlet.collector (current versions should work)
- Update packages showing compatibility warnings during restore

**Package Lock File Regeneration:**
- Delete `src/Dotnet.Samples.AspNetCore.WebApi/packages.lock.json`
- Delete `test/Dotnet.Samples.AspNetCore.WebApi.Tests/packages.lock.json`
- Run `dotnet restore --force-evaluate` to regenerate lock files with .NET 10
compatible package versions

Phase 2: Build Infrastructure Updates

Update Docker configuration and all CI/CD pipelines to use .NET 10 SDK and runtime images.

Task 1: Update Dockerfile Base Images

Modify the Dockerfile to use .NET 10 SDK and runtime images.

• Update Dockerfile SDK image from mcr.microsoft.com/dotnet/sdk:8.0 to mcr.microsoft.com/dotnet/sdk:10.0
• Update runtime image from mcr.microsoft.com/dotnet/aspnet:8.0 to mcr.microsoft.com/dotnet/aspnet:10.0
• Update the LABEL on line 34 to reference ".NET 10 (LTS)" instead of ".NET 8 (LTS)"
• No changes needed to compose.yaml as it references the Dockerfile for build configuration

Task 2: Update Azure Pipelines Configuration

Modify Azure Pipelines to use .NET 10 SDK.

• Update azure-pipelines.yml UseDotNet@2 task version from 8.x to 10.x
• Update any comments or documentation in the file referencing ASP.NET Core 8.0 to 10.0

Task 3: Update GitHub Actions CI Workflow

Modify the continuous integration workflow to use .NET 10.

• Update .github/workflows/dotnet-ci.yml environment variable DOTNET_VERSION from 8.0.x to 10.0.x
• The actions/setup-dotnet action version can remain at v5.1.0 as it supports .NET 10

Task 4: Update GitHub Actions CD Workflow

Modify the continuous deployment workflow to use .NET 10.

• Update .github/workflows/dotnet-cd.yml environment variable DOTNET_VERSION from 8.0.x to 10.0.x
• Verify Docker build steps will work with updated Dockerfile (no additional changes expected)

🤖 Prompt for AI agents

This phase updates all build infrastructure (Docker and CI/CD pipelines) to use
.NET 10 SDK and runtime images consistently across all environments.

**Dockerfile Updates (`Dockerfile`):**
- Change SDK base image from `mcr.microsoft.com/dotnet/sdk:8.0` to
`mcr.microsoft.com/dotnet/sdk:10.0`
- Change runtime base image from `mcr.microsoft.com/dotnet/aspnet:8.0` to
`mcr.microsoft.com/dotnet/aspnet:10.0`
- Update LABEL on line 34 from ".NET 8 (LTS)" to ".NET 10 (LTS)"
- No changes required to compose.yaml

**Azure Pipelines (`azure-pipelines.yml`):**
- Update UseDotNet@2 task version from `8.x` to `10.x`
- Update any comments or documentation referencing ASP.NET Core 8.0 to 10.0

**GitHub Actions CI Workflow (`.github/workflows/dotnet-ci.yml`):**
- Change `DOTNET_VERSION` environment variable from `8.0.x` to `10.0.x`
- Keep actions/setup-dotnet action at v5.1.0 (supports .NET 10)

**GitHub Actions CD Workflow (`.github/workflows/dotnet-cd.yml`):**
- Change `DOTNET_VERSION` environment variable from `8.0.x` to `10.0.x`
- Docker build steps should work with updated Dockerfile without changes

Phase 3: Documentation, Validation, and Release

Update project documentation to reflect .NET 10 requirements, validate the complete upgrade through build and test execution, and prepare the first release.

Task 1: Update README.md

Update the README to reflect .NET 10 as the required framework version.

• Update README.md to change all references from .NET 8 to .NET 10
• Update any prerequisites section to specify .NET 10 SDK requirement
• Update any badges that display .NET version if present
• Update any installation or getting started instructions referencing specific SDK versions

Task 2: Update CHANGELOG.md for Release

Document the .NET 10 upgrade and prepare release notes for v1.0.0-azteca.

• Move content from the [Unreleased] section to a new [1.0.0] - YYYY-MM-DD section in CHANGELOG.md
• Add entries under "Changed" category documenting the .NET 10 LTS upgrade including:
  • Target framework updated from .NET 8 to .NET 10 LTS
  • NuGet packages upgraded to .NET 10 compatible versions (ASP.NET Core 10.0.x, EF Core 10.0.x)
  • Docker images updated to .NET 10 SDK and runtime
  • CI/CD pipelines updated to use .NET 10 SDK
• Note that this release maintains backward compatibility with no breaking API changes
• Reset the [Unreleased] section with empty placeholder categories for future changes

Task 3: Validate Build and Tests

Execute build and test commands to confirm successful upgrade.

• Run dotnet build to verify solution compiles without errors or unexpected warnings
• Run dotnet test to confirm all unit tests pass
• Execute docker build to verify container builds successfully
• Run the container locally to confirm application starts and responds to health check endpoint
• Address any deprecation warnings that surface (particularly around ASP.NET Core 10 breaking changes identified in web search)

Task 4: Create Release Tag

Create and push the version tag to trigger the automated CD workflow for the first release.

• After all changes are merged and validation passes, create the release tag following the project's convention
• Create annotated tag: git tag -a v1.0.0-azteca -m "Release 1.0.0 - Azteca"
• Push the tag to origin: git push origin v1.0.0-azteca
• The CD workflow will automatically build, test, publish Docker images with three tags (:1.0.0, :azteca, :latest), and create the GitHub Release with auto-generated notes
• Verify the GitHub Release is created and Docker images are available in GitHub Container Registry

🤖 Prompt for AI agents

This phase updates project documentation to reflect .NET 10 requirements,
validates the complete upgrade through comprehensive build and test execution,
and prepares the first release (v1.0.0-azteca).

**README.md Updates:**
- Change all references from .NET 8 to .NET 10 throughout the file
- Update prerequisites section to specify .NET 10 SDK requirement
- Update any .NET version badges if present
- Update installation or getting started instructions that reference specific
SDK versions

**CHANGELOG.md Updates for Release:**
- Move content from the `[Unreleased]` section to a new `[1.0.0] - YYYY-MM-DD`
section (use current date)
- Add entries under "Changed" category documenting:
  - Target framework updated from .NET 8 to .NET 10 LTS
- NuGet packages upgraded to .NET 10 compatible versions (ASP.NET Core 10.0.x,
EF Core 10.0.x)
  - Docker images updated to .NET 10 SDK and runtime
  - CI/CD pipelines updated to use .NET 10 SDK
- Note that this release maintains backward compatibility with no breaking API
changes
- Reset the `[Unreleased]` section with empty placeholder categories for future
changes

**Validation Steps:**
- Run `dotnet build` to verify solution compiles without errors or unexpected
warnings
- Run `dotnet test` to confirm all unit tests pass
- Execute `docker build` to verify container builds successfully
- Run the container locally to confirm application starts and responds to health
check endpoint
- Address any deprecation warnings that surface, particularly around ASP.NET
Core 10 breaking changes

**Release Tag Creation:**
- After all changes are merged and validation passes, create annotated tag: `git
tag -a v1.0.0-azteca -m "Release 1.0.0 - Azteca"`
- Push the tag to origin: `git push origin v1.0.0-azteca`
- The CD workflow will automatically build, test, publish Docker images with
three tags (`:1.0.0`, `:azteca`, `:latest`), and create the GitHub Release with
auto-generated notes
- Verify the GitHub Release is created and Docker images are available in GitHub
Container Registry

---

🚀 Next Steps

🤖 All AI agent prompts combined

Task: 1

This phase updates project configuration and dependencies to target .NET 10,
including creating SDK version pinning and upgrading all NuGet packages.

**Target Framework Updates:**
- In
`src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj`,
change `<TargetFramework>net8.0</TargetFramework>` to
`<TargetFramework>net10.0</TargetFramework>`
- In
`test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj`,
change `<TargetFramework>net8.0</TargetFramework>` to
`<TargetFramework>net10.0</TargetFramework>`
- ImplicitUsings and Nullable settings should remain unchanged

**SDK Version Pinning:**
- Create `global.json` in repository root
- Set SDK version to `10.0.100` (or latest stable .NET 10 SDK version)
- Set `rollForward` policy to `latestFeature` for patch updates while
maintaining major version stability

**NuGet Package Updates - Main Project
(`src/Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj`):**
- Update `Microsoft.AspNetCore.OpenApi` from 8.0.23 to 10.0.x
- Update `Microsoft.EntityFrameworkCore.Sqlite` from 9.0.12 to 10.0.x
- Update `Microsoft.EntityFrameworkCore.Design` from 9.0.12 to 10.0.x
- Update `Microsoft.VisualStudio.Web.CodeGeneration.Design` to 10.0.x compatible
version
- Verify `Microsoft.Extensions.Configuration.Json` 10.0.x compatibility
(currently at 10.0.2)
- Keep AutoMapper constraint `[14.0.0,15.0.0)` unchanged
- Keep Serilog, FluentValidation, and Swashbuckle packages at current versions

**NuGet Package Updates - Test Project
(`test/Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj`):**
- Update `Microsoft.NET.Test.Sdk` from 18.0.1 to latest .NET 10 compatible
version
- Verify compatibility of xunit, xunit.runner.visualstudio, Moq,
FluentAssertions, and coverlet.collector (current versions should work)
- Update packages showing compatibility warnings during restore

**Package Lock File Regeneration:**
- Delete `src/Dotnet.Samples.AspNetCore.WebApi/packages.lock.json`
- Delete `test/Dotnet.Samples.AspNetCore.WebApi.Tests/packages.lock.json`
- Run `dotnet restore --force-evaluate` to regenerate lock files with .NET 10
compatible package versions
===============================================================================

Task: 2

This phase updates all build infrastructure (Docker and CI/CD pipelines) to use
.NET 10 SDK and runtime images consistently across all environments.

**Dockerfile Updates (`Dockerfile`):**
- Change SDK base image from `mcr.microsoft.com/dotnet/sdk:8.0` to
`mcr.microsoft.com/dotnet/sdk:10.0`
- Change runtime base image from `mcr.microsoft.com/dotnet/aspnet:8.0` to
`mcr.microsoft.com/dotnet/aspnet:10.0`
- Update LABEL on line 34 from ".NET 8 (LTS)" to ".NET 10 (LTS)"
- No changes required to compose.yaml

**Azure Pipelines (`azure-pipelines.yml`):**
- Update UseDotNet@2 task version from `8.x` to `10.x`
- Update any comments or documentation referencing ASP.NET Core 8.0 to 10.0

**GitHub Actions CI Workflow (`.github/workflows/dotnet-ci.yml`):**
- Change `DOTNET_VERSION` environment variable from `8.0.x` to `10.0.x`
- Keep actions/setup-dotnet action at v5.1.0 (supports .NET 10)

**GitHub Actions CD Workflow (`.github/workflows/dotnet-cd.yml`):**
- Change `DOTNET_VERSION` environment variable from `8.0.x` to `10.0.x`
- Docker build steps should work with updated Dockerfile without changes
===============================================================================

Task: 3

This phase updates project documentation to reflect .NET 10 requirements,
validates the complete upgrade through comprehensive build and test execution,
and prepares the first release (v1.0.0-azteca).

**README.md Updates:**
- Change all references from .NET 8 to .NET 10 throughout the file
- Update prerequisites section to specify .NET 10 SDK requirement
- Update any .NET version badges if present
- Update installation or getting started instructions that reference specific
SDK versions

**CHANGELOG.md Updates for Release:**
- Move content from the `[Unreleased]` section to a new `[1.0.0] - YYYY-MM-DD`
section (use current date)
- Add entries under "Changed" category documenting:
  - Target framework updated from .NET 8 to .NET 10 LTS
- NuGet packages upgraded to .NET 10 compatible versions (ASP.NET Core 10.0.x,
EF Core 10.0.x)
  - Docker images updated to .NET 10 SDK and runtime
  - CI/CD pipelines updated to use .NET 10 SDK
- Note that this release maintains backward compatibility with no breaking API
changes
- Reset the `[Unreleased]` section with empty placeholder categories for future
changes

**Validation Steps:**
- Run `dotnet build` to verify solution compiles without errors or unexpected
warnings
- Run `dotnet test` to confirm all unit tests pass
- Execute `docker build` to verify container builds successfully
- Run the container locally to confirm application starts and responds to health
check endpoint
- Address any deprecation warnings that surface, particularly around ASP.NET
Core 10 breaking changes

**Release Tag Creation:**
- After all changes are merged and validation passes, create annotated tag: `git
tag -a v1.0.0-azteca -m "Release 1.0.0 - Azteca"`
- Push the tag to origin: `git push origin v1.0.0-azteca`
- The CD workflow will automatically build, test, publish Docker images with
three tags (`:1.0.0`, `:azteca`, `:latest`), and create the GitHub Release with
auto-generated notes
- Verify the GitHub Release is created and Docker images are available in GitHub
Container Registry

💡 Iterate on the plan with: @coderabbitai <feedback>

Example Feedback
- @coderabbitai You can skip phase 3. Add a simple unit test case for phase 2.
- @coderabbitai For assumption 1 go ahead with option 3 and replan.

---

💬 Have feedback or questions? Drop into our discord!

[nanotaboada]

@coderabbitai does this change justify cutting a new release?

[coderabbitai]

@nanotaboada Yes, absolutely! This change definitely justifies cutting a new release. Here's why:

Why This Warrants a Release

1. Runtime Requirements Change: Users will need the .NET 10 SDK/runtime installed to run the application. Anyone using your current .NET 8 version cannot simply pull the update without upgrading their environment first.

2. Breaking Change in Deployment: The Docker images, deployment pipelines, and runtime dependencies all change. This affects how users deploy and run the application.

3. LTS-to-LTS Migration: This is a major framework upgrade between Long-Term Support versions, which is a significant milestone worth marking with a proper release.

4. Dependency Graph Changes: All Microsoft packages (ASP.NET Core, EF Core, etc.) are being upgraded to 10.0.x versions, which represents substantial changes to the dependency tree.

Recommended Versioning

Depending on your current versioning scheme:

• Major version bump (e.g., 2.0.0 → 3.0.0) - if you follow strict semantic versioning and consider runtime requirements as breaking changes
• Minor version bump (e.g., 2.1.0 → 2.2.0) - if you consider it a feature upgrade with clear migration path

Optional Considerations

• If you have active users on .NET 8, you might consider maintaining a separate branch for critical fixes
• Tag the last .NET 8 commit clearly (e.g., v2.x-net8-final) before merging the .NET 10 upgrade
• Include migration notes in your release notes highlighting the .NET 10 requirement

The release notes should clearly communicate that .NET 10 SDK is now required, making it easy for users to understand what they need to upgrade.

---

🧠 Learnings used

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: azure-pipelines.yml:0-0
Timestamp: 2026-01-18T04:31:59.110Z
Learning: Applies to **/*.csproj : Target ASP.NET Core projects to .NET 8 for all builds and deployments

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T18:30:02.819Z
Learning: Applies to **/*.{csproj,fsproj} : Project must target .NET 8 (LTS) for consistency across the codebase

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T18:30:02.819Z
Learning: Applies to **/*.{csproj,fsproj} : Use `dotnet add package` command to add package references instead of manually editing project files to maintain lock file integrity

[nanotaboada]

@coderabbitai Analyze the Releases section of the README.md (as well as the CHANGELOG.md if needed) and update the Coding Plan accordingly.

[coderabbitai]

I've updated the plan above based on your feedback. Ready to proceed when you are!

[nanotaboada]

@coderabbitai The initial Release already exists, https://github.com/nanotaboada/Dotnet.Samples.AspNetCore.WebApi/releases/tag/v1.0.0-azteca, maybe there's an issue with the CHANGELOG.md template?

[coderabbitai]

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Read CHANGELOG.md to understand current version state
cat CHANGELOG.md

Length of output: 2741

---

🏁 Script executed:

#!/bin/bash
# Read README.md to check the Releases section
cat README.md

Length of output: 14445

---

🏁 Script executed:

#!/bin/bash
# Check if there are any other tags/releases in the repository
git tag -l

Length of output: 0

---

🏁 Script executed:

#!/bin/bash
# Use GitHub CLI to fetch the release details for v1.0.0-azteca
gh release view v1.0.0-azteca --json tagName,name,body,createdAt,author

Length of output: 88

---

🏁 Script executed:

#!/bin/bash
# Fetch release information using GitHub API
curl -s https://api.github.com/repos/nanotaboada/Dotnet.Samples.AspNetCore.WebApi/releases/tags/v1.0.0-azteca | jq '{tag_name, name, body, created_at, author: .author.login}'

Length of output: 94

---

🏁 Script executed:

#!/bin/bash
# List all releases for the repository
curl -s https://api.github.com/repos/nanotaboada/Dotnet.Samples.AspNetCore.WebApi/releases | jq '[.[] | {tag_name, name, created_at, author: .author.login}]'

Length of output: 68

---

🏁 Script executed:

#!/bin/bash
# List all releases without filtering
curl -s https://api.github.com/repos/nanotaboada/Dotnet.Samples.AspNetCore.WebApi/releases

Length of output: 279

---

@nanotaboada You're absolutely right! I found the issue. There is a documentation gap between the actual GitHub release and the CHANGELOG.md.

The Problem

The release v1.0.0-azteca exists on GitHub (as you confirmed), but CHANGELOG.md was never updated to document it. Looking at the current CHANGELOG.md:

## [Unreleased]

### Added
### Changed
### Fixed
### Removed

There's no [1.0.0 - azteca] section, which means the release was created without following the documented workflow.

What Should Have Happened

According to the "How to Release" section in CHANGELOG.md, the proper workflow is:

1. First: Update CHANGELOG.md with release notes
2. Then: Create and push the tag
3. Finally: CD workflow creates the GitHub release

For v1.0.0-azteca, it appears step 1 was skipped.

Recommendations

1. Retroactively Document v1.0.0-azteca

Add a section to CHANGELOG.md documenting what was included in the initial release:

## [1.0.0 - azteca] - 2025-01-XX

### Added
- Initial release with CRUD operations for football players
- SQLite database with Entity Framework Core
- Swagger/OpenAPI documentation
- Rate limiting and caching
- Docker and Docker Compose support
- Health check endpoint

2. For the .NET 10 Upgrade

The next release should be either:

• v1.1.0-bernabeu (minor version) - if you consider it a non-breaking feature addition
• v2.0.0-bernabeu (major version) - if you consider runtime requirement changes as breaking

I recommend v1.1.0-bernabeu since the API remains backward-compatible (no breaking changes to endpoints or behavior).

3. Updated Plan

The plan needs to target v1.1.0-bernabeu instead of v1.0.0-azteca, and should include:

• Phase 3, Task 2: Add v1.0.0-azteca section retroactively (if desired)
• Phase 3, Task 2: Move unreleased changes to [1.1.0 - bernabeu] section
• Phase 3, Task 4: Create tag v1.1.0-bernabeu

Would you like me to regenerate the plan with these corrections?

---

🧠 Learnings used

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: azure-pipelines.yml:0-0
Timestamp: 2026-01-18T04:31:59.110Z
Learning: Applies to **/*.csproj : Target ASP.NET Core projects to .NET 8 for all builds and deployments

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T18:30:02.819Z
Learning: Applies to **/*.{csproj,fsproj} : Project must target .NET 8 (LTS) for consistency across the codebase

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T18:30:02.819Z
Learning: Applies to **/*.{csproj,fsproj} : Use `dotnet add package` command to add package references instead of manually editing project files to maintain lock file integrity

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: azure-pipelines.yml:0-0
Timestamp: 2026-01-18T04:31:59.110Z
Learning: Applies to **/azure-pipelines.yml : Install .NET 8 SDK with performMultiLevelLookup enabled to allow finding other SDK versions if needed

---

Learnt from: CR
Repo: nanotaboada/Dotnet.Samples.AspNetCore.WebApi PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T18:30:02.819Z
Learning: Run `dotnet build --configuration Release` and ensure it builds successfully before committing