Skip to content

Document package version precedence - #5652

Open
mthalman wants to merge 1 commit into
dotnet:mainfrom
mthalman:mthalman-document-version-precedence
Open

Document package version precedence#5652
mthalman wants to merge 1 commit into
dotnet:mainfrom
mthalman:mthalman-document-version-precedence

Conversation

@mthalman

Copy link
Copy Markdown
Member

Problem

Existing source-build documentation did not fully explain how PSB, current source-built, and shared-component package versions interact. In particular, it could imply that *PreviousVersion guarantees PSB provenance and did not document the full import precedence.

Solution

Make package-dependency-flow.md the canonical reference by documenting:

  • Generated Previous, Current, SharedComponents, Snapshot, and aggregate props files.
  • Import order: Previous → Current → SharedComponents.
  • MSBuild’s last-assignment-wins behavior.
  • Why *PreviousVersion does not guarantee final provenance.
  • How provenance-sensitive components should preserve versions in component-specific properties with standalone-build fallbacks.

The overview and feature-band guides now link to this canonical explanation rather than duplicating it.

Co-authored-by: Copilot App 223556219+Copilot@users.noreply.github.com

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 126c96ee-7cea-466b-89b0-e526394c4d93
@mthalman
mthalman requested a review from a team as a code owner August 21, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants