Clarify feature band source-build inputs - #5630
Merged
mthalman merged 4 commits intoAug 13, 2026
Merged
Conversation
Document how lifecycle-relative inputs map to the exact versions configured by a VMR revision, and clarify host versus target inputs for cross-builds. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3746ac39-bec0-467f-8aaf-7ed30f38df0b
mthalman
marked this pull request as ready for review
August 5, 2026 17:19
lbussell
approved these changes
Aug 12, 2026
Comment on lines
+283
to
+284
| - **Initial Release (N.0.200)**: Current source-built 1xx shared component | ||
| artifacts + previous source-built 1xx artifacts and SDK |
Member
There was a problem hiding this comment.
The 2xx section and the 3xx/4xx sections are very similar. It seems like the 2xx sections 3xx/4xx could be combined into a 2xx+ section and use the text from the 3xx/4xx section. Is my understanding correct?
Feel free to dismiss if this is outside the scope of these changes.
| `build.sh` script and pass the extracted artifact directory for the | ||
| required 1xx version. | ||
|
|
||
| **Error**: Package-source mapping or package-version resolution failures after |
Member
There was a problem hiding this comment.
nit: other troubleshooting entries use specific error text here whereas this one doesn't look like a specific error.
Comment on lines
+821
to
+822
| components caused `Microsoft.NETCore.Platforms` resolution to fail. That | ||
| failure was an unsupported input matrix, not a general 2xx defect. |
Member
There was a problem hiding this comment.
Suggested change
| components caused `Microsoft.NETCore.Platforms` resolution to fail. That | |
| failure was an unsupported input matrix, not a general 2xx defect. | |
| components causes `Microsoft.NETCore.Platforms` resolution to fail because | |
| the inputs did not match the versions expected by the build. |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3746ac39-bec0-467f-8aaf-7ed30f38df0b
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3746ac39-bec0-467f-8aaf-7ed30f38df0b
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: 3746ac39-bec0-467f-8aaf-7ed30f38df0b
lbussell
approved these changes
Aug 12, 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
2 participants
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.
Higher feature-band source builds can fail when inputs are selected by recency rather than by the versions configured in the VMR revision being built. This clarifies how distro maintainers should interpret lifecycle-relative "current" and "previous" inputs while reproducing a specific branch, tag, or commit. It also provides guidance on cross-build scenarios.