Merged
Conversation
Per some team discussion, the old changewave pace doesn't make a ton of
sense if we're releasing monthly. Let's
* Be more willing to create new changewaves
* Always match them to the current development version
And we also decided last year that we would wait until the release
corresponding to a .NET SDK major version to actually remove waves.
Writing that down!
Also added an agent skill to refer to these docs to help, so you can
/changewaves Wrap this call in a changewave
And it will (if all goes well) handle it for you.
Contributor
There was a problem hiding this comment.
Pull request overview
Updates MSBuild Change Wave documentation and adds an agent skill to standardize how new wave-gated changes are introduced, versioned, and retired in a monthly release cadence.
Changes:
- Updates public/internal Change Wave docs to encourage creating waves aligned to the current in-development MSBuild version and documents wave retirement timing.
- Adds a new agent skill (
/changewaves) to guide creating/using/documenting/retiring change waves.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| documentation/wiki/ChangeWaves.md | Clarifies permanence/retirement guidance and restructures sections describing active and retiring waves. |
| documentation/wiki/ChangeWaves-Dev.md | Updates developer guidance for selecting the appropriate wave based on the in-development MSBuild version. |
| .github/skills/changewaves/SKILL.md | Introduces an agent skill with lifecycle guidance and a checklist for wave-gated changes. |
MichalPavlik
approved these changes
Feb 23, 2026
AR-May
approved these changes
Feb 23, 2026
Member
AR-May
left a comment
There was a problem hiding this comment.
LGTM. The only thing I noticed is some inconsistency in terminology across the repo (“change wave” vs. “changewave”).
5 tasks
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
JanProvaznik
pushed a commit
to JanProvaznik/msbuild
that referenced
this pull request
Feb 25, 2026
Per some team discussion, the old changewave pace doesn't make a ton of
sense if we're releasing monthly. Let's
* Be more willing to create new changewaves
* Always match them to the current development version
And we also decided last year that we would wait until the release
corresponding to a .NET SDK major version to actually remove waves.
Writing that down!
Also added an agent skill to refer to these docs to help, so you can
/changewaves Wrap this call in a changewave
And it will (if all goes well) handle it for you.
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This was referenced Feb 25, 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.
Per some team discussion, the old changewave pace doesn't make a ton of
sense if we're releasing monthly. Let's
And we also decided last year that we would wait until the release
corresponding to a .NET SDK major version to actually remove waves.
Writing that down!
Also added an agent skill to refer to these docs to help, so you can
And it will (if all goes well) handle it for you.