Bump streetsidesoftware/cspell-action from 8.4.0 to 9.0.1 in the actions-deps group - #443
Conversation
Bumps the actions-deps group with 1 update: [streetsidesoftware/cspell-action](https://github.com/streetsidesoftware/cspell-action). Updates `streetsidesoftware/cspell-action` from 8.4.0 to 9.0.1 - [Release notes](https://github.com/streetsidesoftware/cspell-action/releases) - [Changelog](https://github.com/streetsidesoftware/cspell-action/blob/main/CHANGELOG.md) - [Commits](streetsidesoftware/cspell-action@de2a73e...e0668cf) --- updated-dependencies: - dependency-name: streetsidesoftware/cspell-action dependency-version: 9.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: actions-deps ... Signed-off-by: dependabot[bot] <support@github.com>
## Why The .NET 10 SDK dropped the VSTest bridge `dotnet test` relied on, so `dotnet test` failed outright on every PR: `Testing with VSTest target is no longer supported by Microsoft.Testing.Platform on .NET 10 SDK and later.` This is what was blocking #443, #444, #445, and #446 (all four currently fail on the `Run unit tests job`). ## What - Opt `UtilitiesTests` into native Microsoft.Testing.Platform (MTP): `global.json`'s `test.runner` setting, plus `UseMicrosoftTestingPlatformRunner`/`OutputType=Exe` on the test project, per the [official migration guide](https://learn.microsoft.com/en-us/dotnet/core/testing/migrating-vstest-microsoft-testing-platform). - Swap `coverlet.collector` (VSTest-only) for `Microsoft.Testing.Extensions.CodeCoverage`, the native MTP coverage provider. - Bump `Microsoft.NET.Test.Sdk` and the `xunit.v3` family to the versions that ship a compatible MTP runtime; the prior `xunit.v3` 3.2.2 pairing threw a `TypeLoadException` against the newer platform assembly. - Update the validate workflow's `dotnet test` invocation (`--coverage` instead of `--collect`), naming the output file explicitly (`--coverage-output coverage.cobertura.xml`): the extension's default GUID basename is not matched by codecov-action's file finder, so the upload step would otherwise silently find nothing under `fail_ci_if_error: false`. - Fix three `ExtensionsTests.cs` null-argument tests that were missing the null-forgiving operator a sibling test already used; `TreatWarningsAsErrors` never reached these under the old VSTest error, which aborted the build before the test project ever compiled. - Add `global.json` to the Solution Items folder and fix `Directory.Packages.props`'s alphabetical ordering. ## Verification Ran locally against .NET 10.0.400: `dotnet build` (0 warnings/errors), `dotnet test --coverage --coverage-output-format cobertura --coverage-output coverage.cobertura.xml --results-directory ./coverage` (183/183 passed, `coverage/coverage.cobertura.xml` produced), `dotnet csharpier check .`, and `dotnet format style --verify-no-changes` all clean. Reviewed with a local adversarial pass before pushing (fleet `local-strict-review`). ## Known trade-off `Microsoft.Testing.Extensions.CodeCoverage` ships native instrumentation for `win-x64/x86/arm64`, `linux-x64`, `linux-musl-x64`, and `osx-x64` only, no `osx-arm64` or `linux-arm64`. CI runs on `ubuntu-latest` (x64) and is unaffected, but coverage collection won't work locally on Apple Silicon or Linux arm64 dev machines, where `coverlet.collector` had none of that restriction. Flagging for awareness rather than blocking on it, since this is the officially recommended MTP coverage path. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Updated the test runner and testing tools for improved compatibility and execution. * Added consistent Cobertura code coverage reporting. * Preserved validation of expected compression and decompression errors. * **Chores** * Standardized .NET SDK and test environment configuration. * Updated test tooling and coverage integration packages. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
## Why Same regression as #447, on `main` this time (per `.github/dependabot.yml`, `main` and `develop` are kept current independently). The .NET 10 SDK dropped the VSTest bridge `dotnet test` relied on, so `dotnet test` failed outright: `Testing with VSTest target is no longer supported by Microsoft.Testing.Platform on .NET 10 SDK and later.` This is what was blocking #443 and #444 (both currently fail on the `Run unit tests job`). ## What Identical fix to #447, cherry-picked (the relevant files were byte-identical between `main` and `develop` before this PR): - Opt `UtilitiesTests` into native Microsoft.Testing.Platform (MTP) via `global.json`'s `test.runner` setting plus `UseMicrosoftTestingPlatformRunner`/`OutputType=Exe`. - Swap `coverlet.collector` (VSTest-only) for `Microsoft.Testing.Extensions.CodeCoverage` (native MTP coverage), marked test-only via `PrivateAssets`. - Bump `Microsoft.NET.Test.Sdk`/`xunit.v3`/`xunit.analyzers`/`xunit.runner.visualstudio` to versions with a compatible MTP runtime. - Update the validate workflow's `dotnet test` invocation (`--coverage` instead of `--collect`, with an explicit `--coverage-output` filename codecov-action can discover). - Fix three `ExtensionsTests.cs` null-argument tests missing a null-forgiving operator. - `global.json` in CRLF (this repo's `.editorconfig` convention) and added to Solution Items. ## Verification Already went through #447's full review loop (local adversarial review, Copilot, CodeRabbit, all findings fixed) on identical content. Re-verified independently on this branch: `dotnet build` (0 warnings/errors), `dotnet test --coverage --coverage-output-format cobertura --coverage-output coverage.cobertura.xml --results-directory ./coverage` (183/183 passed), `dotnet csharpier check .`, `dotnet format style --verify-no-changes`, and `editorconfig-checker` on `global.json` all clean. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Tests** * Updated automated test execution with a modern test runner for more reliable validation. * Added improved code coverage collection and Cobertura report generation for clearer quality metrics. * Updated testing tools and frameworks to newer versions. * Preserved existing compression test behavior while improving nullable-value handling during test execution. * **Chores** * Added centralized configuration for consistent test tooling across the solution. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
…451) Brings this repository back into line with the hub, driven from `RESYNC.md` against a fresh hub checkout. The audit that produced the findings ran at `audit run 2026-08-30T03:27:29Z | hub a378121` and reported 45 findings against `main@eb80a36`. Every hub task is pinned at `f3b4cc9`, release `2.0.526`. ## Line endings are now LF This is the headline change and the reason nearly every file appears in the diff. The fleet standard moved to LF, so `.gitattributes` is now `* text=auto eol=lf` with CRLF kept only for `*.bat` and `*.cmd`, and `.editorconfig` declares `end_of_line = lf` on `[*]` with the same single CRLF exception. The two now agree, and git enforces on checkout what the editor writes, where the old `* -text` default left git out of it entirely. The tree was renormalized with `git add --renormalize`, so every tracked file is LF in both the index and the working tree. Verified against the hub's own gate: ```text [ok ] eol 0 issue(s) [ok ] eol-coverage 0 issue(s) (9 representative paths + 1 tracked shebang path resolved through git check-attr) ``` **Reviewing this diff:** 52 of the 124 changed files carry line-ending churn and nothing else, and are provably byte-identical with the carriage returns stripped. `git diff origin/develop --ignore-cr-at-eol` is the view that drops them. ## Instruction set `AGENTS.md` is now the hub's three byte-locked sections plus a repository preamble, with the fleet rule text moved to a new `GOVERNANCE.md` (the 20 declared sections) and a new `CLAUDE.md` importing `AGENTS.md`. `CODESTYLE.md`, `WORKFLOW.md` and `AUDIT.md` are re-vendored, and the `.github/skills/` tree is carried whole with its digest verified against the hub source. The `carried-instruction-file-guard` probe found twelve local additions in the old `AGENTS.md` and `CODESTYLE.md`. None were dropped. Each went to its declared destination: | Local content | Destination | | --- | --- | | Library public-API and behavioral contracts, project layout | new `ARCHITECTURE.md` | | Tooling, linter invocations, release and hook runbooks | new `OPERATIONS.md` | | Packable-project, test-runner and analyzer-relaxation rules | `CODESTYLE.md` "Utilities .NET Conventions" | ## Workflows All four reusable tasks are now the hub's, reached by pin: `validate-task`, `publish-plan-task`, `build-release-task` and `merge-bot-task`. What stays here is the trigger policy, the paths filter, the per-target wiring, and the ruleset-bound aggregator. `build-release-task.yml`, `publish-plan-task.yml`, `validate-task.yml`, `repo-config/` and `spec/secrets.json` are deleted, per their `retire` dispositions in the hub's `spec/divergences.json`. Adopting the shared validator was originally deferred, because its unit-test step ran the VSTest coverage invocation that this repository's native Microsoft.Testing.Platform suite exits `5` on. Hub #1107 fixed that in `2.0.526`, and the task's exact command was verified against this tree before adopting: 183 of 183 pass, and the report lands where the Codecov finder matches it once prefixed. Both Codecov checks are green on this pull request, which is the end-to-end proof. The pull request workflow also gained the `changes` paths filter that `WORKFLOW.md` D1.1, D1.4 and D1.5 require. Its entries are the publisher's own shipped-input list, so the smoke gate and the publish gate agree on what affects the package by construction, and a documentation-only pull request now skips the smoke build. ## Dependabot PRs #443 through #446 are stale against this branch: they still carry `coverlet.collector`, which the Microsoft.Testing.Platform migration removed, and they conflict. Their content is either already on `develop` or included here (the cspell action at `v9.0.1`). Dependabot should reopen cleanly once `develop` and `main` move. Also bumps `Microsoft.Testing.Extensions.CodeCoverage` to 18.10.0, the one package with an update available. The dotnet tool manifest is already at the current CSharpier and Husky.Net. ## Verification Every gate run locally before each push, plus three `local-strict-review` passes whose findings are all fixed: ```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 cspell README.md HISTORY.md 0 issues actionlint clean editorconfig-checker clean shellcheck + shfmt (.husky/pre-commit) clean repo_gate.py eol, eol-coverage, sha-pin all clean prose_lint.py --diff origin/develop clean ``` ## Filed rather than fixed here - #452, the download tests reaching real network hosts. Correct, and out of scope for a change that only renormalizes those files' line endings. - Three hub-side items, since no hub file is touched by this change: the carried-content defects this review surfaced, the `WORKFLOW.md` D1.6 wording on how `CODECOV_TOKEN` reaches the validator, and the stale registry entry for this repository. Repository settings and rulesets were not applied, since `repo-config/configure.sh check|apply` is an outward-facing write. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Added architecture, governance, operations, coding standards, audit, workflow, and maintenance guidance. * Improved README navigation, installation, release, contribution, and support information. * Added comprehensive review, testing, and workflow references. * **Workflow Updates** * Streamlined pull-request validation, release planning, publishing, and merge automation. * Removed obsolete validation and release workflow components. * **Consistency** * Standardized line endings, formatting, linting exclusions, and editor configuration. * Improved project and workspace organization. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Looks like streetsidesoftware/cspell-action is no longer updatable, so this is no longer needed. |
Pull request was closed
Bumps the actions-deps group with 1 update: streetsidesoftware/cspell-action.
Updates
streetsidesoftware/cspell-actionfrom 8.4.0 to 9.0.1Release notes
Sourced from streetsidesoftware/cspell-action's releases.
Changelog
Sourced from streetsidesoftware/cspell-action's changelog.
... (truncated)
Commits
e0668cfchore(main): release 9.0.1 (#2734)ed61a9efix: make sure the dictionaries are up to date. (#2733)a670ca8chore(main): release 9.0.0 (#2682)7319e02ci: Workflow Bot -- Update ALL Dependencies (main) (#2732)ffbcf8fchore: Set pnpm minimumReleaseAge (#2731)c48ca1cchore: Update PNPM (#2664)c223c96chore(deps-dev): bump tsdown from 0.21.10 to 0.22.14 (#2721)f433a62fix: Workflow Bot -- Update ALL Dependencies (main) (#2710)7a30246fix: Update Dictionaries and Dependencies (#2729)7f801dafix: Update Dictionaries and Dependencies (#2717)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