Update changelogs for MTP 2.3.2 / MSTest 4.3.2 release#9898
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7cfde194-252a-4b69-8647-62f7964fb4e4
There was a problem hiding this comment.
Pull request overview
Adds release notes for the upcoming servicing release built from rel/4.3, documenting MSTest 4.3.2 and Microsoft.Testing.Platform 2.3.2.
Changes:
- Add a new
[4.3.2]section todocs/Changelog.mdwith the two user-facing MSTest changes. - Add a new
[2.3.2]section todocs/Changelog-Platform.mdnoting version alignment and no functional platform changes.
Show a summary per file
| File | Description |
|---|---|
| docs/Changelog.md | Adds the MSTest 4.3.2 release section and links to the relevant PRs/compare view. |
| docs/Changelog-Platform.md | Adds the MTP 2.3.2 release section indicating a servicing alignment release. |
Review details
- Files reviewed: 2/2 changed files
- Comments generated: 2
- Review effort level: Low
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7cfde194-252a-4b69-8647-62f7964fb4e4
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 7cfde194-252a-4b69-8647-62f7964fb4e4
There was a problem hiding this comment.
Note
🤖 Automated review by GitHub Copilot. Generated by the Expert Code Review workflow. To request a follow-up action, reply by tagging @copilot directly.
Review Summary
This PR makes two categories of changes:
- XLF localization files — transitions from
state="new"tostate="translated"with actual translated content across 13 languages. - TODO comment cleanup — rewrites bare
TODOcomments as plain explanatory comments, complying with the repository TODO policy.
Findings
⚠️ Localization — Confirm XLF generation method (Dimension 22: Localization Done Right)
The repository guidelines state: "NEVER manually modify *.xlf files. Instead, regenerate them by running dotnet msbuild <project>.csproj /t:UpdateXlf."
The XLF changes here add real translations (not just copying English source text), which suggests these came from a localization servicing system (e.g., OneLocBuild or a translation vendor drop). Could the author confirm these were produced by an automated localization pipeline rather than hand-edited? If they were machine-generated by the loc system, this is fine — the guideline is primarily aimed at preventing developers from hand-editing translations.
✅ TODO Comment Policy (Dimension 6)
All TODO removals look correct. The comments are rewritten as plain explanatory notes that describe the situation without creating an action item. None of the remaining comments require a tracking issue since they no longer use the TODO keyword.
✅ No Public API Changes (Dimension 4)
No public API surface changes detected.
✅ Code Style (Dimension 7)
The rewritten comments read naturally and maintain the existing indentation and formatting conventions.
No blocking issues found. The only open question is confirming the XLF generation method.
What
Adds the changelog sections for the upcoming servicing release (built from
rel/4.3, versions 4.3.2 / 2.3.2).docs/Changelog.md— new[4.3.2]section (Changed)ReflectionFreethe defaultMSTestSourceGenModefor Native AOT / trimmed consumers — #9777docs/Changelog-Platform.md— new[2.3.2]sectionHow the content was derived
Diffed
v4.3.0..origin/rel/4.3(7 commits). Only #9777 and #9825 are user-facing; the remaining commits are localization backports (not changelogged per repo convention), version bumps, and post-release bookkeeping. Both functional PRs touch MSTest only (src/Adapter,src/Analyzers/Shared,src/Package/MSTest.Sdk); none touchsrc/Platform, hence no MTP entries.Needs attention / manual review
2026-07-13. Update if tagging happens on a different day.rel/4.3(notmain); the PR link still resolves.