Comparing changes

Updated [Microsoft.Extensions.Http.Resilience](https://github.com/dotnet/extensions) from 10.7.0 to 10.8.0. <details> <summary>Release notes</summary> _Sourced from [Microsoft.Extensions.Http.Resilience's releases](https://github.com/dotnet/extensions/releases)._ ## 10.8.0 This release adds new experimental APIs to Microsoft.Extensions.AI.Abstractions and updates the OpenAI dependency to 2.12.0, alongside documentation, test, and repository maintenance. ## Experimental API Changes ### New Experimental APIs * New experimental API: `AIFunctionNameAttribute` and `AIParameterNameAttribute` #7610 by @jozkee (co-authored by @jeffhandley @Copilot) * New experimental API: `ToolApprovalRequestContent.RequiresConfirmation` (`MEAI001`) #7549 by @javiercn (co-authored by @Copilot) ## What's Changed ### AI * Upgrade OpenAI dependency to 2.12.0 #7608 by @jozkee (co-authored by @Copilot) * Auto-detect audio format in OpenAISpeechToTextClient #7575 by @jozkee (co-authored by @Copilot) * Fix ToolJson.AdditionalProperties to accept sub-schema objects #7546 by @jozkee (co-authored by @Copilot) * Fix ImageGeneratingChatClient duplicating preceding content and dropping following content #7624 by @jozkee (co-authored by @Copilot) ### Vector Data * Make all test methods virtual in VectorData.ConformanceTests #7606 by @adamsitnik (co-authored by @Copilot) ## Documentation Updates * Remove links to ai-samples repo #7574 by @gewarren * Fix up docs with Copilot (MEVD) #7597 by @gewarren * Fix up docs with Copilot (M.E.ServiceDiscovery) #7598 by @gewarren (co-authored by @Copilot) * Fix up docs with Copilot (MEAI) #7600 by @gewarren * Fix up docs with Copilot #7601 by @gewarren ## Test Improvements * Fix flaky StampedeTests and harden related test waits #7572 by @jeffhandley (co-authored by @Copilot) * Fix SQLitePCLRaw.lib.e_sqlite3 vulnerability by replacing SemanticKernel connectors with CommunityToolkit #7579 by @adamsitnik (co-authored by @Copilot) * Removing SemanticKernel Connectors dependency and replacing it #7584 by @adamsitnik (co-authored by @Copilot) * Migrate to xUnit v3 #7607 by @adamsitnik (co-authored by @shyamnamboodiripad @Copilot) ## Repository Infrastructure Updates * Update OTel GenAI conventions skill for standalone semconv-genai repo #7519 by @jeffhandley (co-authored by @Copilot) * Bump dotnet-coverage from 18.7.0 to 18.8.0 #7552 * [main] Update dependencies from dotnet/arcade #7559 * Fix transitive MessagePack vulnerability in AI template AppHost projects #7561 by @adamsitnik (co-authored by @Copilot) * Bump esbuild, @vitejs/plugin-react and vite in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7564 * Bump tmp from 0.2.6 to 0.2.7 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7569 * Bump js-yaml from 4.1.1 to 4.2.0 in /src/Libraries/Microsoft.Extensions.AI.Evaluation.Reporting/TypeScript #7570 * Bump PowerShell from 7.6.2 to 7.6.3 #7576 * Remove duplicate 'WebAPI' classification from template #7577 by @danroth27 * [main] Update dependencies from dotnet/arcade #7590 * Eliminate redundant Correctness CI stage by merging into Build #7594 by @adamsitnik (co-authored by @Copilot) ... (truncated) Commits viewable in [compare view](dotnet/extensions@v10.7.0...v10.8.0). </details> Updated [Microsoft.Extensions.Logging.Abstractions](https://github.com/dotnet/dotnet) from 10.0.9 to 10.0.10. <details> <summary>Release notes</summary> _Sourced from [Microsoft.Extensions.Logging.Abstractions's releases](https://github.com/dotnet/dotnet/releases)._ No release notes found for this version range. Commits viewable in [compare view](https://github.com/dotnet/dotnet/commits). </details> Updated [Microsoft.SourceLink.GitHub](https://github.com/dotnet/dotnet) from 10.0.300 to 10.0.301. <details> <summary>Release notes</summary> _Sourced from [Microsoft.SourceLink.GitHub's releases](https://github.com/dotnet/dotnet/releases)._ ## 10.0.301 You can build .NET 10.0 from the repository by cloning the release tag `v10.0.301` and following the build instructions in the [main README.md](https://github.com/dotnet/dotnet/blob/v10.0.301/README.md#building). 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](https://github.com/dotnet/dotnet/blob/v10.0.301/README.md#building-from-released-sources). 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](dotnet/dotnet@v10.0.300...v10.0.301). </details> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will 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 version` will 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 </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Docs-only change: appends a new list item 3 "Spelling CI scope" to the Markdown and Spelling section of CODESTYLE.md, propagating the template's CODESTYLE Spelling-CI-scope rule (ptr727/ProjectTemplate#302, #303). It documents that the CI spell-check gate covers README.md + HISTORY.md only, not all markdown, with broad live checking left to the cspell editor extension. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Cherry-picks the CODESTYLE "Spelling CI scope" documentation onto main, without dragging the unrelated in-flight work currently on develop. Docs-only; the same change is already on develop. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

Bumps the actions-deps group with 1 update: [actions/setup-dotnet](https://github.com/actions/setup-dotnet). Updates `actions/setup-dotnet` from 5.4.0 to 6.0.0 - [Release notes](https://github.com/actions/setup-dotnet/releases) - [Commits](actions/setup-dotnet@26b0ec1...a98b568) --- updated-dependencies: - dependency-name: actions/setup-dotnet dependency-version: 6.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions-deps ... Signed-off-by: dependabot[bot] <[email protected]>

…417) Implements the fleet hub drift finding (ProjectTemplate #330): earlier downstream carries drifted from the current repo-config and merge-bot reference. ## Repo-config carry refresh - Rename `repo-config/ruleset-develop.json` and `ruleset-main.json` to `develop.json` and `main.json`, matching the current fleet reference layout (the fleet audit letter-checks the new paths). - Refresh `README.md`, `configure.sh`, and `settings.json` to the current reference content. ## Self-audit carry - Add `AUDIT.md` at the repo root plus `spec/secrets.json` per the repo-config Downstream Carry, adapted from the blessed Vantage-Config reference for this repo's release model with the nuget-oidc and codecov secret mechanisms. ## Merge-bot workflow sync - Sync `.github/workflows/merge-bot-pull-request.yml` to the current fleet reference: notably `gh pr merge` no longer uses `--delete-branch`, and the header and comments are updated. ## Scope Live rulesets, settings, and secrets were verified in sync with the reference payloads today; this change touches committed files only. No live repo configuration was modified. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Follow-up to the conformance audit for #387 (finding 1, analyzer suppression hygiene). ## What prompted this [CODESTYLE.md](../blob/develop/CODESTYLE.md) "Analyzer Suppressions" names `dotnet_analyzer_diagnostic.severity` as the exact anti-pattern it forbids -- relaxing a batch of rules repo-wide -- yet the root `.editorconfig` carried it. ## What removing it surfaced Exactly one rule, and none of it in shipping code: | Rule | Sites | Project | | --- | --- | --- | | xUnit1051 | 29 | UtilitiesTests | `Utilities` and `Sandbox` produced **zero** findings under `AnalysisLevel=latest-all` + `AnalysisMode=All`. I re-ran with `-p:EnforceCodeStyleInBuild=true` to confirm IDE analyzers were not being silently skipped -- same result. The relaxation was hiding nothing in library code. xUnit1051 is a true positive, not a suppression candidate: it asks that async calls in tests pass `TestContext.Current.CancellationToken` so xUnit v3 can cancel a stalled test. The clearest case is `DownloadAsyncTests`, which makes real network calls and previously had no cancellation path if a request hung. ## Audit of every other suppression Each was removed and rebuilt independently to prove it is load-bearing. All of them are -- kept, no changes: | Suppression | Scope | Fires when removed | Verdict | | --- | --- | --- | --- | | `CA1711` | Utilities | yes | Deliberate `Ex` suffix convention | | `CA1707` | UtilitiesTests | yes | xUnit `Method_Scenario_Expected` naming | | `CA1515` | UtilitiesTests | yes | xUnit needs public test classes | | `NoWarn IL3058` | Utilities, Sandbox | yes (10 under `PublishAot=true`) | Polly/Serilog not annotated AOT-compatible; no source location to scope | | `IDE0055` | root | no | Inert today, but CSharpier owns formatting; kept as a guard, now with a rationale comment | The naming-rule severities were also raised to `warning` as a probe and produced nothing. ## Verification - `dotnet build -c Release` with `TreatWarningsAsErrors` intact: 0 warnings, 0 errors - `dotnet test -c Release`: 183/183 passed - `dotnet format style --verify-no-changes`: clean - CSharpier + `dotnet format` Husky hooks passed on commit ## Notes No `Closes #387` here -- per [AGENTS.md](../blob/develop/AGENTS.md) "Branching Model", closing keywords belong in the `develop -> main` promotion PR. #387's other three findings (inline pragmas, `GlobalUsings.cs`, stale package source) were already resolved in earlier work and need no change. A fleet-wide issue is being filed against ProjectTemplate, since LanguageTags carries the identical `dotnet_analyzer_diagnostic` line and the other repos have not been probed. Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Coverage has been uploaded to Codecov since the coverage workflow landed (#377), but the README never surfaced it. Adds a Coverage shield to the **Build Status** block, following the badge pattern used in [aiopurpleair](https://github.com/ptr727/aiopurpleair): ```markdown [![Release Status][releasebuildstatus-shield]][actions-link]\ [![Last Commit][lastcommit-shield]][commits-link]\ [![Coverage][coverage-shield]][coverage-link] ``` Shield and link definitions were inserted in the file's existing alphabetical order, between `commits-link` and `github-link`. ## Verification - Shield URL returns HTTP 200 and renders real data (`coverage: 67%`), not `unknown` - markdownlint MD052 (undefined reference) clean -- both definitions resolve - CRLF preserved - No `cspell.json` change needed: `codecov` is not flagged (aiopurpleair carries the same badge with no dictionary entry), and README is in the CI spell-check scope per CODESTYLE Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Promotion of the current `develop` integration state to `main`. ## Contents | Area | Change | | --- | --- | | Analyzer conformance | #418 -- removed the repo-wide `dotnet_analyzer_diagnostic` relaxation, fixed the 29 `xUnit1051` sites it hid | | Docs | #419 -- Codecov coverage shield in the README build status block | | Repo config | #417 -- repo-config carry refresh and self-audit carry | ## Conformance issues resolved Closes #380 Closes #387 #380 (xUnit v3 + AwesomeAssertions, `ILoggerFactory` seam) was already satisfied in the tree -- verified rather than assumed: 0 `Assert.*` remaining against 245 `.Should()` calls, `xunit.v3` 3.2.2 pinned with no v2 package, zero Serilog references in the library, and `Utilities/LogOptions.cs` matching the LanguageTags reference seam. #387's four findings were likewise already addressed except finding 1 (analyzer suppression hygiene), which #418 closes. Every remaining suppression was independently probed by removing it and rebuilding, and all proved load-bearing (`CA1711`, `CA1707`, `CA1515`, `NoWarn IL3058`). ## Release impact: no auto-publish This promotion carries **no shipped input**. Per [WORKFLOW.md](../blob/main/WORKFLOW.md) the inclusion list is `Utilities/**`, `version.json`, `Directory.Build.props`, `Directory.Packages.props`; this diff is confined to tests, docs, CI, and repo config: ``` .editorconfig .github/workflows/merge-bot-pull-request.yml AUDIT.md README.md UtilitiesTests/*.cs repo-config/* spec/secrets.json ``` `Utilities/**` is byte-identical between `main` and `develop`, so the published package is already current and merging this will correctly **not** trigger a stable release.

Fixes both items in #421, surfaced by Copilot review on #420. ## 1. `configure.sh check` / `apply` do not exist `WORKFLOW.md` referenced subcommands the script never implemented. Its interface is `[owner/repo] [release|operational]`, so `configure.sh check` parses `check` as a **repository name** -- it acts on the wrong target rather than erroring, which is why this was worth fixing rather than leaving. Auditing also moved to [`AUDIT.md`](../blob/develop/AUDIT.md) as a read-only procedure; `configure.sh` now only applies. Updated: - **5D Configuration audit** -- points at the AUDIT.md procedure - **Validation** (section 6) -- AUDIT.md audits read-only, `configure.sh [owner/repo] [release|operational]` applies - Two residual phrases that still described the script as the auditor ("applied and audited by an idempotent `gh api` script", "the script flags it as a manual verification item") ## 2. `NUGET_USERNAME` secret store `WORKFLOW.md` said Actions-store-only; `spec/secrets.json` and `AUDIT.md` say both stores. Resolved in favor of both, on two pieces of evidence: - The fleet hub's canonical `nuget-oidc` mechanism in `ProjectTemplate/spec/secrets.json` declares `"stores": ["actions", "dependabot"]`, and this repo's spec is a carry of it - Live repository state has the name in both stores ``` actions: CODECOV_TOKEN CODEGEN_APP_CLIENT_ID CODEGEN_APP_PRIVATE_KEY NUGET_USERNAME dependabot: CODECOV_TOKEN CODEGEN_APP_CLIENT_ID CODEGEN_APP_PRIVATE_KEY NUGET_USERNAME ``` So `WORKFLOW.md` was the outlier. It now states both stores and cites the spec it follows. Worth recording: Copilot predicted this would make the self-audit report a false defect. It would not -- the secret is present in both stores, so the audit passes today. The defect was purely that three documents disagreed. ## Correction to the issue's fleet note #421 speculated these might need upstream fixes too. Checked, and they do not: ProjectTemplate's `WORKFLOW.md` has no `configure.sh` subcommand references and no NuGet publish at all. Both drifts are local to this repo. ## Verification - No `configure.sh check|apply` references remain - All three link targets resolve (`AUDIT.md`, `spec/secrets.json`, `repo-config/configure.sh`) - CRLF preserved; docs-only, no shipped input, so no release impact --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Follow-up to #422, from Copilot review on the promotion PR #423. `AUDIT.md` is explicitly read-only: its secrets check is ```sh grep -qx "$s" <<<"$names" && echo "$store/$s: present" || echo "$store/$s: MISSING (defect)" ``` -- `echo`-based, with no defined non-zero exit contract. But two `WORKFLOW.md` sentences still said the audit "asserts" the names exist and "fail[s] if it cannot query them". That wording is a leftover from when `configure.sh check` performed the audit and exited non-zero on drift; #422 moved the audit to AUDIT.md but left these two clauses describing the old behavior. Both now describe what AUDIT.md actually does: check the names, and report a missing name or a failed query as a defect. The App-installation sentence was adjusted for the same reason ("notes rather than fails" -> "notes rather than reports a defect"). Docs-only; no shipped input, so no release impact. Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Promotion of the `WORKFLOW.md` drift fix to `main`. ## Contents | PR | Change | | --- | --- | | #422 | Correct the 5D audit references (`configure.sh check`/`apply` -> AUDIT.md) and the `NUGET_USERNAME` secret store | Closes #421 ## What was fixed 1. **`configure.sh check` / `apply` do not exist.** The script's interface is `[owner/repo] [release|operational]`, so `check` parsed as a *repository name* -- acting on the wrong target rather than erroring. Auditing moved to `AUDIT.md` as a read-only procedure; `configure.sh` only applies. 2. **`NUGET_USERNAME` store.** `WORKFLOW.md` claimed Actions-only while `spec/secrets.json` and `AUDIT.md` claimed both. Resolved in favor of both, matching the fleet hub's canonical `nuget-oidc` mechanism and live repository state (the name is present in both stores). Two further accuracy fixes came out of review: the NuGet.org trusted-publishing policy is now correctly described as sitting *outside* AUDIT.md's drift report, and the `configure.sh` model argument note now covers the no-registry fallback to `release`. ## Release impact: no auto-publish Docs-only. No shipped input (`Utilities/**`, `version.json`, `Directory.Build.props`, `Directory.Packages.props`) is touched, so this will correctly not trigger a stable release. NuGet stays at 4.0.18, whose library content is already identical to `main`.

Closes the terminology nit Copilot raised on #423, which I deferred there as out of scope for that promotion. `strict-off` appeared exactly once in `WORKFLOW.md` (the 5D audit summary). Section 6 spells the same setting out twice: - `main`: `"require branches up to date before merging" is **off**` - `develop`: `"up to date" is **off**` The summary now uses the section 6 phrasing, so both places name the setting identically. The word "strict" survives at line 646 (`so the strict check would fail every release`), which is correct -- that sentence is explaining *why* the setting is off, and "the strict check" is GitHub's own term for the behavior. Docs-only; no shipped input, so no release impact. --------- Co-authored-by: Claude Opus 4.8 (1M context) <[email protected]>

Promotion of #425 to `main`. ## Contents | PR | Change | | --- | --- | | #425 | Spell out the up-to-date ruleset setting in the 5D audit summary | Replaces the one-off `strict-off` term with section 6's phrasing (`"require branches up to date before merging"` **off**), so the audit summary and the ruleset description name the setting identically. Review also caught that the first attempt split the quoted label across a line break, making it unsearchable -- fixed, and the paragraph reflowed to the file's ~105-character width after earlier edits had left a 142-character line. This closes out the terminology finding Copilot raised on #423, which was deferred there as out of scope for that promotion. ## Release impact: no auto-publish Docs-only. No shipped input touched, so no stable release fires. NuGet stays at 4.0.18.

Bumps the actions-deps group with 1 update: [DavidAnson/markdownlint-cli2-action](https://github.com/davidanson/markdownlint-cli2-action). Updates `DavidAnson/markdownlint-cli2-action` from 24.0.0 to 24.1.0 - [Release notes](https://github.com/davidanson/markdownlint-cli2-action/releases) - [Commits](DavidAnson/markdownlint-cli2-action@8de2aa0...6bf21b0) --- updated-dependencies: - dependency-name: DavidAnson/markdownlint-cli2-action dependency-version: 24.1.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: actions-deps ... Signed-off-by: dependabot[bot] <[email protected]>

Bumps AwesomeAssertions from 9.4.0 to 9.5.0 --- updated-dependencies: - dependency-name: AwesomeAssertions dependency-version: 9.5.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-deps ... Signed-off-by: dependabot[bot] <[email protected]>

Updated [AwesomeAssertions](https://github.com/AwesomeAssertions/AwesomeAssertions) from 9.4.0 to 9.5.0. <details> <summary>Release notes</summary> _Sourced from [AwesomeAssertions's releases](https://github.com/AwesomeAssertions/AwesomeAssertions/releases)._ ## 9.5.0  ## What's Changed ### New features * Add [Not]BeDecoratedWith for ParameterInfo by @cbersch in AwesomeAssertions/AwesomeAssertions#449 * Add AssertionChain.ForCondition with lazy condition by @misirlou-tg in AwesomeAssertions/AwesomeAssertions#511 ### Improvements * Return AndWhichConstraint from IntersectWith by @misirlou-tg in AwesomeAssertions/AwesomeAssertions#495 * Return AndWhichConstraint from XElementAssertions.HaveAttribute by @misirlou-tg in AwesomeAssertions/AwesomeAssertions#504 * Fix for #521: Re-wrote `GivenSelector<T>.FailWith()` to match `AssertionChain.FailWith()` by @JakenVeina in AwesomeAssertions/AwesomeAssertions#522 ### Fixes * Fix AssertionResultSet by @cbersch in AwesomeAssertions/AwesomeAssertions#535 * Fix NotSupportedException from ReduceConstantSubExpressions by @cbersch in AwesomeAssertions/AwesomeAssertions#538 * Ensured WithTracing is safe when used with BeEquivalentTo globally by @cbersch in AwesomeAssertions/AwesomeAssertions#539 * Prevent a crash while formatting a collection with nested empty subcollections by @cbersch in AwesomeAssertions/AwesomeAssertions#542 ### Others * Use identical extensions from reflectify by @cbersch in AwesomeAssertions/AwesomeAssertions#444 * chore: upgrade F# lang to 8.0 and Microsoft.Build.Tasks.Core to 18.3.3 by @ScarletKuro in AwesomeAssertions/AwesomeAssertions#461 * Fix build project by @cbersch in AwesomeAssertions/AwesomeAssertions#482 * Fix build project by @cbersch in AwesomeAssertions/AwesomeAssertions#491 * Fix build project by @cbersch in AwesomeAssertions/AwesomeAssertions#492 * Code cleanup in the tests by @lg2de in AwesomeAssertions/AwesomeAssertions#383 * Removing duplicate ForConditions() in two TypeAssertions methods by @misirlou-tg in AwesomeAssertions/AwesomeAssertions#512 * Remove UWP Specs by @cbersch in AwesomeAssertions/AwesomeAssertions#514 * Switch to fork of NUKE: Fallout by @IT-VBFK in AwesomeAssertions/AwesomeAssertions#537 * Prepare docs for 9.5.0 release by @cbersch in AwesomeAssertions/AwesomeAssertions#543 ### Dependencies * chore(deps): update dependency verify.xunit to 31.12.5 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#439 * chore(deps): update dependency meziantou.analyzer to 2.0.302 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#437 * chore(deps): update dependency cspell to v9.7.0 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#445 * chore(deps): update dependency tunit to 1.17.11 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#446 * chore(deps): update dependency meziantou.analyzer to v3 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#448 * chore(deps): update dependency coverlet.collector to v8 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#447 * chore(deps): update dependency microsoft.testing.extensions.codecoverage to 18.5.1 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#451 * chore(deps): update dependency meziantou.analyzer to 3.0.18 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#450 * chore(deps): update dependency tunit to 1.18.9 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#453 * chore(deps): update dependency reflectify to 1.8.0 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#452 * chore(deps): update github artifact actions (major) by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#460 * chore(deps): update dependency microsoft.testing.extensions.codecoverage to 18.5.2 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#458 * chore(deps): update dependency meziantou.analyzer to 3.0.23 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#457 * chore(deps): update dependency tunit to 1.19.57 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#459 * chore(deps): update dependency system.reflection.metadata to 10.0.5 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#462 * chore(deps): update dependency coverlet.collector to 8.0.1 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#463 * chore(deps): update dependency tunit to 1.21.6 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#465 * chore(deps): update dependency meziantou.analyzer to 3.0.27 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#464 * chore(deps): update dependency meziantou.analyzer to 3.0.29 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#466 * chore(deps): update dependency tunit to 1.22.6 - autoclosed by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#467 * chore(deps): update dependency meziantou.analyzer to 3.0.39 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#468 * chore(deps): update dependency tunit to 1.24.0 by @renovate[bot] in AwesomeAssertions/AwesomeAssertions#469 ... (truncated) Commits viewable in [compare view](AwesomeAssertions/AwesomeAssertions@9.4.0...9.5.0). </details> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=AwesomeAssertions&package-manager=nuget&previous-version=9.4.0&new-version=9.5.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore <dependency name> major version` will 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 version` will 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 </details>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comparing changes

Open a pull request

Commits on Jul 15, 2026

Commits on Jul 16, 2026

Commits on Jul 18, 2026

Commits on Jul 20, 2026

This comparison is taking too long to generate.

Uh oh!