docs: add Changed section for MSTEST0050 severity Error→Warning (#9670)#9691
Merged
Conversation
…hangelog.md MSTEST0050 (GlobalTestFixtureShouldBeValidAnalyzer) was lowered from Error to Warning in #9670 to match the six peer fixture analyzers (MSTEST0008-0013). This change is tracked in AnalyzerReleases.Unshipped.md but was missing from the Changelog.md 4.3.0 section. Fixes #9688 Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Adds missing release-note coverage for an analyzer severity change in MSTest’s changelog so that the 4.3.0 (unreleased) entry matches what was already recorded in analyzer release notes.
Changes:
- Add a new
### Changedsection under the 4.3.0 (unreleased) entry. - Document the
MSTEST0050severity downgrade fromErrortoWarning(from PR #9670).
Show a summary per file
| File | Description |
|---|---|
| docs/Changelog.md | Adds a Changed section for 4.3.0 unreleased and documents the MSTEST0050 severity change. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Low
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Note
🤖 Automated review by GitHub Copilot. Posted via a maintainer's GitHub token, so it appears under their account — the account owner did not write or approve this content personally. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.
✅ 22/22 dimensions clean — no findings.
Scope: Documentation-only change (docs/Changelog.md). Verified that:
- The
### Changedsection is correctly placed after### Fixedper [Keep a Changelog]((keepachangelog.com/redacted) conventions - The content accurately reflects the severity change in merged PR #9670 (MSTEST0050: Error → Warning)
- The PR link and author attribution are correct
0101
approved these changes
Jul 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #9688
PR #9670 lowered
MSTEST0050(GlobalTestFixtureShouldBeValidAnalyzer) fromErrortoWarningto match the six peer fixture analyzers (MSTEST0008–0013). This severity change is already tracked inAnalyzerReleases.Unshipped.mdbut was not reflected indocs/Changelog.md.This PR adds a
### Changedsection to the 4.3.0 unreleased entry with one bullet documenting the rule-severity downgrade.Before:
[GlobalTestInitialize]/[GlobalTestCleanup]with invalid signature → build error (hard breaks build)After: Same → build warning (doesn't fail build unless
TreatWarningsAsErrorsis set)