Skip to content

fix: handle private project references in generated release plans - #26

Merged
ScottishTapWater merged 1 commit into
feat/cli-applyfrom
fix/private-project-references
Oct 28, 2026
Merged

ScottishTapWater merged 1 commit into
feat/cli-applyfrom
fix/private-project-references

Conversation

@ScottishTapWater

Copy link
Copy Markdown
Contributor

Summary

  • Keep private project references in the graph used for build order, release propagation and referenced-package versions.
  • Exclude evaluated PrivateAssets="all" references from the package dependencies expected in generated manifests.
  • Add discovery and planner regressions plus two end-to-end tests of the same cascading private-reference release: streamed plan stdout into apply stdin, and plan --outfile followed by apply --infile.

Stacked on #25. Resolves the blocker found during the fresh whole-stack review without weakening archive verification.

Verification

  • Full solution: 140 tests passed.
  • dotnet format src/PackageCascade.slnx --verify-no-changes --no-restore.
  • git diff --check.
  • Independent production and test reviews passed; the original reviewer confirmed the blocker is resolved.

@ScottishTapWater ScottishTapWater changed the title Fix private project references in generated release plans fix: handle private project references in generated release plans Oct 28, 2026
@ScottishTapWater
ScottishTapWater merged commit c182bd0 into main Oct 28, 2026
4 checks passed
@ScottishTapWater
ScottishTapWater deleted the fix/private-project-references branch October 28, 2026 17:52
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.

1 participant