Bump AwesomeAssertions and 3 others - #449
Conversation
Bumps AwesomeAssertions from 9.5.0 to 9.6.0 Bumps Microsoft.Extensions.Http.Resilience from 10.8.0 to 10.9.0 Bumps Microsoft.Extensions.Logging.Abstractions from 10.0.10 to 10.0.11 Bumps Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400 --- updated-dependencies: - dependency-name: AwesomeAssertions dependency-version: 9.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps - dependency-name: Microsoft.Extensions.Http.Resilience dependency-version: 10.9.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps - dependency-name: Microsoft.Extensions.Logging.Abstractions dependency-version: 10.0.11 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-deps - dependency-name: Microsoft.SourceLink.GitHub dependency-version: 10.0.400 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-deps ... Signed-off-by: dependabot[bot] <support@github.com>
Uh oh!
There was an error while loading. Please reload this page.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@## develop #449 +/- ##
========================================
Coverage 67.24% 67.24% ========================================
Files 13 13 Lines 1154 1154 Branches 106 106 ========================================
Hits 776 776 Misses 338 338 Partials 40 40 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Promotes the hub resync (#451) to `main`. ## Why this is a `promote/` branch rather than `develop` itself `main` carried its own copies of work `develop` had done independently: the Microsoft.Testing.Platform migration (#448 against #447) and an AwesomeAssertions bump (#450 against #449). Combined with the CRLF-to-LF renormalization, `develop -> main` conflicts on seven paths, and `develop`'s `required_linear_history` plus its PR ruleset forbid resolving them on `develop`. This is the documented remedy: resolve on a throwaway branch off `main`, then open that into `main`. ## The resolution is provably exactly `develop` Every conflict was resolved to `develop`'s side, and the result is byte-identical to `develop`'s tree: ```text merged tree 5035943 develop tree 5035943 ``` Each was confirmed lossless before `develop` was taken, per the documented check: | Path | Why taking `develop` drops nothing | | --- | --- | | `global.json` | Content-identical modulo EOL. `main` added it CRLF, `develop` renormalized it. | | `UtilitiesTests/UtilitiesTests.csproj` | Content-identical modulo EOL. | | `UtilitiesTests/ExtensionsTests.cs` | Content-identical modulo EOL. | | `Directory.Packages.props` | Differs in one line, the coverage extension, where `develop` is the newer 18.10.0 against `main`'s 18.9.0. | | `Utilities.slnx` | `main`'s extra entries are a duplicate `dependabot.yml`, a `Data/` folder naming three files this repository does not contain, and the two workflow tasks `develop` deleted because the hub now hosts them. Verified each path is absent on `develop`, and that `dependabot.yml` is still listed there under GitHub Actions. | | `.github/workflows/build-release-task.yml` | Deleted on `develop` per its `retire` disposition. | | `.github/workflows/validate-task.yml` | Deleted on `develop`, which now calls the hub-hosted validator by pin. | ## Verification Run against this branch's tree, not inferred from #451: ```text dotnet build 0 warnings, 0 errors dotnet csharpier check . 43 files, clean dotnet format style --verify-no-changes clean dotnet test (MTP + coverage) 183/183 passed markdownlint-cli2 '**/*.md' 48 files, 0 issues actionlint clean editorconfig-checker clean repo_gate.py eol, eol-coverage, sha-pin all clean prose_lint.py --diff origin/main clean ``` ## Merging The head is `promote/develop-to-main`, not `develop`, so the delete-`develop` trap does not apply here. Merge with a merge commit rather than a squash, per the `main` ruleset. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added a `StringHistory` utility for retaining and rendering configurable first and last lines. - Added comprehensive repository architecture, operations, governance, and contribution guidance. - **CI/CD** - Updated validation, testing, and publishing workflows with clearer triggers, scoped permissions, and external workflow integration. - Removed obsolete release and validation workflow definitions. - **Documentation** - Added coding, testing, review, release, and workflow guidance. - **Style** - Standardized text line endings and formatting across the repository. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Updated AwesomeAssertions from 9.5.0 to 9.6.0.
Release notes
Sourced from AwesomeAssertions's releases.
9.6.0
What's Changed
New features
Fixes
Documentation
Others
Dependencies
New Contributors
... (truncated)
Commits viewable in compare view.
Pinned Microsoft.Extensions.Http.Resilience at 10.9.0.
Release notes
Sourced from Microsoft.Extensions.Http.Resilience's releases.
10.9.0
Version 10.9.0 is headlined by changes in these areas:
RoutingChatClientbase class, withSemanticRoutingChatClientas a concrete semantic-routing implementation. Separately, the abstractFailoverChatClientspecialization and its concreteOrderedFailoverChatClientimplementation add failover routing.Experimental API Changes
New Experimental APIs
EXTEXP0013) #7602MEAI001) #7662What's Changed
AI (
Microsoft.Extensions.AI,Microsoft.Extensions.AI.Abstractions, andMicrosoft.Extensions.AI.OpenAI)Note: Microsoft.Extensions.AI.OpenAI constrains its dependency for OpenAI to 2.12.x, preventing OpenAI updates to 2.13.0+ due to an incompatibility. We expect to release Microsoft.Extensions.AI.OpenAI version 10.9.1 during the week of August 17 to address this issue.
HTTP Resilience and Diagnostics (
Microsoft.Extensions.Http.ResilienceandMicrosoft.Extensions.Http.Diagnostics)ASP.NET Core Extensions (
Microsoft.AspNetCore.Diagnostics.Middleware)Logging Source Generator (
Microsoft.Gen.Logging)AI Evaluation (
Microsoft.Extensions.AI.Evaluation.Reporting)Project Templates (
Microsoft.McpServer.ProjectTemplates)... (truncated)
10.8.4
This servicing update refreshes the .NET AI project templates ahead of the July 30, 2026 retirement of GitHub Models — removing the GitHub Models provider option and updating template dependencies.
As a result, both the AI Chat Web (
aichatweb) and AI Agent Web API (aiagent-webapi) templates now require the AI service provider to be chosen explicitly via--provider; there is no longer a default. One of the following must be selected:--provider azureopenai— Azure OpenAI--provider ollama— Ollama (for local development)--provider openai— OpenAI PlatformPackages in this release
What's Changed
Project templates
--provideroption is now required with no default (#7667).Aspire.Hosting.AppHostto13.4.6andCommunityToolkit.VectorData.SqliteVecto1.0.0-preview.4(alignedSystem.Linq.AsyncEnumerableto10.0.9), replacing earlier workaround package pins (#7639).Full Changelog
10.8.3
Packages in this release
Experimental API Changes
Experimental API behavior updates
ToolApprovalRequestContent.RequiresConfirmationso it no longer leaks into consumer source-generatedAIContentJSON metadata unless approval APIs are intentionally used (#7659).What's Changed
AI abstractions and serialization
RequiresConfirmationin source-generatedAIContentcontexts by using an internal JSON-included backing member while keeping the public experimental member ignored for source-generation metadata (#7659).Test Improvements
List<AIContent>contexts compile and round-trip without requiring MEAI001 suppression (#7659).Full Changelog
10.8.2
This servicing release updates Microsoft.Extensions.VectorData.ConformanceTests to 10.8.2 and includes targeted test framework migration fixes.
Packages in this release
Update: August 7, 2026
The Microsoft.Extensions.VectorData.Abstractions package was initially excluded from this release by mistake. Because Microsoft.Extensions.VectorData.ConformanceTests has a dependency on Microsoft.Extensions.VectorData.Abstractions, that led to failures when updating to Microsoft.Extensions.VectorData.ConformanceTests 10.8.2.
Microsoft.Extensions.VectorData.Abstractions was published August 7, 2026 to resolve that issue.
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.1...v10.8.2
10.8.1
This servicing release updates the Microsoft.Extensions.AI, Microsoft.Extensions.AI.Abstractions, and Microsoft.Extensions.AI.OpenAI packages to 10.8.1 with two targeted fixes: correct tool-call/tool-result ordering when resuming approval-gated functions with service-managed chat history, and preservation of the OpenAI Responses reasoning item id for stateless (store=false) encrypted reasoning.
Packages in this release
What's Changed
AI
Acknowledgements
Full Changelog: dotnet/extensions@v10.8.0...v10.8.1
Commits viewable in compare view.
Pinned Microsoft.Extensions.Logging.Abstractions at 10.0.11.
Release notes
Sourced from Microsoft.Extensions.Logging.Abstractions's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.SourceLink.GitHub from 10.0.301 to 10.0.400.
Release notes
Sourced from Microsoft.SourceLink.GitHub's releases.
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions