You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Use incremental API diffs for preview migration guidance - #10599
Review each preview or RC milestone's API diff for migration candidates (Preview 1 compares with the previous stable GA, while later milestones compare with the preceding prerelease); verify them against milestone PRs, changes.json, the build, and maintained samples rather than copying diff entries into release notes.
Separate Breaking changes from .NET N (N is the previous stable major version; version-to-version compatibility changes) from Changes since the previous preview (changes affecting only users of this major's earlier prereleases, including RCs). Include the former in preview notes and confirm coverage in the new version's aggregate compatibility documentation; omit empty sections and do not duplicate changes.
Cross-check the target version's .NET and ASP.NET Core compatibility indexes, open and closed announcement issues, and upstream breaking-change PRs. These sources may be incomplete or published after the change ships, so establish the milestone using changes.json and build evidence. Flag missing aggregate coverage to the component owner.
If the diff is unavailable, try generating it; if that fails, track the pending review on the base PR while drafting, and do not finalize without reviewing the report or recording a component-owner exception. Recheck pending diffs on populated milestone branches and incorporate newly published compatibility guidance even if the build has not changed.
This is separate from #10596, which covers where maintained samples live and how to validate them.
Validation
Targeted Markdown lint and link checks on the edited skill files passed; git diff --check passed.
Prettier reports formatting warnings for the edited files, consistent with the repository-wide baseline. Checkov could not run: Checkov and a Python installer are unavailable on this machine.
Use compatibility catalogs, announcements, implementation PRs, changes.json, and build evidence to identify version-to-version breaks without treating any source as complete.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 637615df-deba-4407-bf00-9a3bd4e569b5
The reason will be displayed to describe this comment to others. Learn more.
Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.
Note
This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.
Select the GA baseline for Preview 1, use versioned compatibility indexes, and track failed diff generation through release-note reruns.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 637615df-deba-4407-bf00-9a3bd4e569b5
This sentence only directs the writer to compare against the previous stable release, which is insufficient to distinguish a preview-only migration: an API or behavior introduced in Preview 6 and changed in Preview 7 must also be compared with Preview 6. The neighboring upgrade guidance requires both baselines; otherwise breaking_changes: true entries can be put in the wrong section.
Compare first previews with the previous stable release and later prereleases with both stable and preceding shipped prerelease baselines.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 7e7e9011-e85b-469d-88f5-7843d1de691f
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
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
changes.json, the build, and maintained samples rather than copying diff entries into release notes.breaking-changePRs. These sources may be incomplete or published after the change ships, so establish the milestone usingchanges.jsonand build evidence. Flag missing aggregate coverage to the component owner.This is separate from #10596, which covers where maintained samples live and how to validate them.
Validation
git diff --checkpassed.