.NET: 2026-09-18 Release version bump

[westey (westey-m)]

Motivation & Context

Description & Review Guide

• What are the major changes?
• What is the impact of these changes?
• What do you want reviewers to focus on?

Related Issue

Fixes #

Contribution Checklist

• The code builds clean without any errors or warnings
• All unit tests pass, and I have added new tests where possible
• The PR follows the Contribution Guidelines
• This PR is linked to an issue and there is no other open PR for this issue (see Related Issue above).
• This is not a breaking change. If it is a breaking change, add the breaking change label (or add "[BREAKING]" to the title prefix, before or after any language prefix) — a workflow keeps the label and title prefix in sync automatically.

[Copilot]

🟡 Changes recommended

The package-validation baseline must advance to 1.21.0 before releasing 1.22.0.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Advances the central .NET package release metadata to 1.22.0.

Changes:

• Bumps package version to 1.22.0.
• Updates preview date suffix.
• Derives GitTag from VersionPrefix.

File summaries

File	Description
dotnet/nuget/nuget-package.props	Updates central release metadata.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Balanced

---

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

[github-actions]

MAF Automated Review — Iteration 1

Result: No findings
Scope: full PR (1 commit(s)): b3e2d04f25f5
Model: gpt-5.6-sol-fast

Overview

This PR centrally advances the .NET package version and date while deriving GitTag from the same VersionPrefix source of truth. Direct MSBuild evaluation produces the expected GA, RC, and preview versions, and the repository's .NET CI builds, packs, installs, and consumer-builds the resulting packages. No PR-introduced Critical, High, or Medium defect was established.

Reviewed the supplied pull-request change set across correctness, security/reliability, architecture, and failure behavior.
No publishable findings remained after source verification for this scope.