[gimlichael]

This pull request moves the library, its tests and its tooling from the .NET 9 baseline to .NET 11 and .NET 10. It also converts the codebase to file-scoped namespaces, refreshes package versions and brings CI, DocFX and contributor guidance in line with the new targets.

Library source:

• Production types use file-scoped namespaces, matching the enforced editorconfig rule.

Build and CI configuration:

• Shared build props, the SDK pin and the solution file target .NET 11 and .NET 10.
• Package versions are refreshed to the latest stable releases, and the Asp.Versioning 9 package group is dropped.
• CI runs on Ubuntu 26.04 with preview SDKs so the .NET 11 targets are built and tested before the stable release.

Test suite:

• Test assets and test cases use file-scoped namespaces.
• The endpoint builder finalizer fixture is added with the tests that use it.
• The YAML error response test expects the ASP.NET Core 11 middleware frame name on each target while keeping the full response assertion.

Release notes and changelog:

• The 11.0.0 changelog entry and package release notes record the move from .NET 9 to .NET 11 for consumers.

Documentation:

• README, agent guidance, contributing notes and DocFX availability includes state .NET 11 and .NET 10 as the supported targets.

Repository configuration:

• Editor and line-ending rules are aligned with the repository's LF policy.
• Dependabot, Codecov and gitignore settings are updated, and the .bot readme is tracked as the ignore rules allow.

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The package's framework support changes for its consumers, while its runtime API stays the same.

The PR appears safe to merge, with a non-blocking fix recommended for caching missing docs assets.

Findings

1.  Missing assets stay cached ▶

Fix with agent prompt

### Issue 1
.docfx/nginx.conf:14
Adding `always` sends the year-long `Cache-Control` header on 404 responses too. If a browser requests a new asset while an older docs container still serves traffic, `try_files` returns 404 and the browser can cache that failure for a year, even after deployment finishes. Remove `always` from this header so failed requests do not receive the permanent cache policy.

```suggestion
        add_header Cache-Control "public, max-age=31536000, immutable";
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

Moves the library and tests to .NET 11 and .NET 10, updates dependencies, and converts remaining namespaces to file-scoped declarations.

• The library and its tests target .NET 11 and .NET 10.
• C# files use file-scoped namespaces, and the editor flags other styles.
• The YAML response test checks the middleware frame name for each target framework.
• DocFX points its sitemap at the asp-versioning site host.
• Repository settings and guidance follow updated conventions.

_{Reviews (1) · Last reviewed commit: "📝 track the .bot readme that .gitignore..." · Reviewed by Greptile}

[greptile-apps]

Missing assets stay cached

Adding always sends the year-long Cache-Control header on 404 responses too. If a browser requests a new asset while an older docs container still serves traffic, try_files returns 404 and the browser can cache that failure for a year, even after deployment finishes. Remove always from this header so failed requests do not receive the permanent cache policy.

Suggested change

	add_header Cache-Control "public, max-age=31536000, immutable" always;
	add_header Cache-Control "public, max-age=31536000, immutable";

Prompt To Fix With AI

This is a comment left during a code review.
Path: .docfx/nginx.conf
Line: 14

Comment:
**Missing assets stay cached**

Adding `always` sends the year-long `Cache-Control` header on 404 responses too. If a browser requests a new asset while an older docs container still serves traffic, `try_files` returns 404 and the browser can cache that failure for a year, even after deployment finishes. Remove `always` from this header so failed requests do not receive the permanent cache policy.

```suggestion
        add_header Cache-Control "public, max-age=31536000, immutable";
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud