Clarify feature band source-build inputs - #5630
Open
mthalman wants to merge 1 commit into
Open
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
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.
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.