Added instructions for identifying changes specific to a subset of TFMs and OSes, where applicable.#4243
Open
paulmedynski wants to merge 2 commits intomainfrom
Open
Added instructions for identifying changes specific to a subset of TFMs and OSes, where applicable.#4243paulmedynski wants to merge 2 commits intomainfrom
paulmedynski wants to merge 2 commits intomainfrom
Conversation
…Ms and OSes, where applicable.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release-notes generation prompt to explicitly guide how to identify and annotate changes that only apply to certain Target Frameworks (TFMs) and/or operating systems, based on source-level evidence.
Changes:
- Adds instructions to determine per-PR TFM scope using file naming, conditional compilation, and build conditions.
- Adds instructions to determine per-PR OS scope using file naming, preprocessor symbols, and OS-gated build logic.
- Updates the release-notes writing instructions to include TFM/OS qualifiers when changes are not universal across supported targets.
mdaigle
previously approved these changes
Apr 28, 2026
cheenamalhotra
previously approved these changes
Apr 29, 2026
apoorvdeshmukh
previously approved these changes
Apr 29, 2026
priyankatiwari08
previously approved these changes
Apr 29, 2026
paulmedynski
dismissed stale reviews from priyankatiwari08, apoorvdeshmukh, cheenamalhotra, and mdaigle
via
1c2b6a2
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.
Summary
Enhances the
release-notesprompt with explicit guidance for identifying and annotating changes that only affect a subset of the driver's supported targets.Changes
New Step 2.1 — TFM Scope Detection
Instructs the agent to examine each PR's changed files and code for framework-specific evidence before writing release notes:
.netfx.cs,.netcore.cs#if NETFRAMEWORK,#if NETConditionexpressions onTargetFramework/TargetFrameworksWhen a change is framework-scoped, the generated note includes a concise qualifier such as
(net462 only)or(net8.0/net9.0 only). Universal changes get no qualifier.New Step 2.2 — OS Scope Detection
Mirrors Step 2.1 for operating-system-specific changes:
.windows.cs,.unix.cs#if _WINDOWS,#if _UNIXTargetOs/NormalizedTargetOsconditionsWhen a change is OS-scoped, the note includes a qualifier such as
(Windows only)or(Unix only). When both TFM and OS are scoped they are combined: e.g.(net8.0/net9.0 on Windows only).Updated Step 5.2 — Generation Requirement
The release-notes writing step now explicitly requires TFM and OS qualifiers to be included for any Added/Changed/Fixed/Removed item where Step 2.1 or Step 2.2 identifies non-universal scope.
Checklist