Bump version to 10.1.0 for next development cycle

[Copilot]

Now that the 10.0 release branch has been cut, the main branch needs to target 10.1 development.

Changes

• Updated MinorVersion from 0 to 1 in eng/Versions.props

This changes the repository version from 10.0.0-preview.1 to 10.1.0-preview.1. All generated packages and assemblies will now use the 10.1 version prefix.

Original prompt

Update repository branding to begin 10.1 development now that 10.0 has branched.

Scope (mechanical version bump only):

1. eng/Versions.props

   • Change from 0 to 1 (MajorVersion stays 10, PatchVersion stays 0).
   • Leave PreReleaseVersionLabel (preview) and PreReleaseVersionIteration (1) as-is unless already incremented elsewhere.

2. Assembly / metadata branding

   • Update any assembly metadata or manifest files that carry the four-part assembly version from 10.0.0.0 to 10.1.0.0. (Based on prior PR Update repository branding from 9.10 to 10.0 #6907 this includes: src/Libraries/Microsoft.Extensions.AmbientMetadata.Application/Microsoft.Extensions.AmbientMetadata.Application.json.)

3. Template integration test snapshot projects
   Replace package version references for repository-produced packages that were set to 10.0.0 in the previous branding PR with 10.1.0:

   • Microsoft.Extensions.AI
   • Microsoft.Extensions.AI.OpenAI
   • Microsoft.Extensions.Http.Resilience

   The prior 10.0 branding PR (Update repository branding from 9.10 to 10.0 #6907) touched the following 8 snapshot .csproj files; update them again:

   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.AzureOpenAI_Qdrant_Aspire.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.AzureOpenAI_Qdrant_Aspire.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Basic.verified/aichatweb/aichatweb.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.BasicAspire.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.BasicAspire.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Ollama_Qdrant.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Ollama_Qdrant.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.OpenAI_AzureAISearch.verified/aichatweb/aichatweb.csproj

4. Search for any remaining hard-coded "10.0.0" or "10.0.0.0" occurrences referring to these packages/assembly versions in snapshots or metadata and update to 10.1.0 / 10.1.0.0. Do NOT alter dependency versions for external packages (e.g., SemanticKernel, OpenTelemetry, Aspire components) even if they include 10.0 numbers—only our produced packages.

Non-goals:

• Do not change dependency versions coming from Arcade/Maestro or third-party packages.
• Do not modify PreReleaseVersionLabel or iteration.
• No code or logic changes—mechanical substitutions only.

Validation Steps:

• Build repository (./build or equivalent) to ensure no versioning tasks fail.
• Run the template integration tests to regenerate/verify snapshots; ensure they pass with updated versions.
• Confirm no lingering references to 10.0.0* for the targeted packages via a repo grep.

Deliverables:

• A PR on top of main updating the above files.
• PR title: "Update repository branding from 10.0 to 10.1".
• PR description should summarize changes (similar style to PR Update repository branding from 9.10 to 10.0 #6907) and list updated files.

Rationale:
Main is moving to 10.1 servicing/development now that 10.0 has branched, so branded version needs to reflect new minor train for produced packages and templates.

This pull request was created as a result of the following prompt from Copilot chat.

Update repository branding to begin 10.1 development now that 10.0 has branched.

Scope (mechanical version bump only):

1. eng/Versions.props

   • Change from 0 to 1 (MajorVersion stays 10, PatchVersion stays 0).
   • Leave PreReleaseVersionLabel (preview) and PreReleaseVersionIteration (1) as-is unless already incremented elsewhere.

2. Assembly / metadata branding

   • Update any assembly metadata or manifest files that carry the four-part assembly version from 10.0.0.0 to 10.1.0.0. (Based on prior PR Update repository branding from 9.10 to 10.0 #6907 this includes: src/Libraries/Microsoft.Extensions.AmbientMetadata.Application/Microsoft.Extensions.AmbientMetadata.Application.json.)

3. Template integration test snapshot projects
   Replace package version references for repository-produced packages that were set to 10.0.0 in the previous branding PR with 10.1.0:

   • Microsoft.Extensions.AI
   • Microsoft.Extensions.AI.OpenAI
   • Microsoft.Extensions.Http.Resilience

   The prior 10.0 branding PR (Update repository branding from 9.10 to 10.0 #6907) touched the following 8 snapshot .csproj files; update them again:

   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.AzureOpenAI_Qdrant_Aspire.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.AzureOpenAI_Qdrant_Aspire.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Basic.verified/aichatweb/aichatweb.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.BasicAspire.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.BasicAspire.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Ollama_Qdrant.verified/aichatweb/aichatweb.ServiceDefaults/aichatweb.ServiceDefaults.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.Ollama_Qdrant.verified/aichatweb/aichatweb.Web/aichatweb.Web.csproj
   • test/ProjectTemplates/Microsoft.Extensions.AI.Templates.IntegrationTests/Snapshots/aichatweb.OpenAI_AzureAISearch.verified/aichatweb/aichatweb.csproj

4. Search for any remaining hard-coded "10.0.0" or "10.0.0.0" occurrences referring to these packages/assembly versions in snapshots or metadata and update to 10.1.0 / 10.1.0.0. Do NOT alter dependency versions for external packages (e.g., SemanticKernel, OpenTelemetry, Aspire components) even if they include 10.0 numbers—only our produced packages.

Non-goals:

• Do not change dependency versions coming from Arcade/Maestro or third-party packages.
• Do not modify PreReleaseVersionLabel or iteration.
• No code or logic changes—mechanical substitutions only.

Validation Steps:

• Build repository (./build or equivalent) to ensure no versioning tasks fail.
• Run the template integration tests to regenerate/verify snapshots; ensure they pass with updated versions.
• Confirm no lingering references to 10.0.0* for the targeted packages via a repo grep.

Deliverables:

• A PR on top of main updating the above files.
• PR title: "Update repository branding from 10.0 to 10.1".
• PR description should summarize changes (similar style to PR Update repository branding from 9.10 to 10.0 #6907) and list updated files.

Rationale:
Main is moving to 10.1 servicing/development now that 10.0 has branched, so branded version needs to reflect new minor train for produced packages and templates.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Microsoft Reviewers: Open in CodeFlow