Skip to content

Add readme steps on how to validate external packages within a full source-build #1448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Oct 31, 2025
Merged

Add readme steps on how to validate external packages within a full source-build #1448

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1ff6637
Add readme steps on how to validate external packages within a full s…
MichaelSimons Oct 29, 2025
5868e80
Merge branch 'main' into readme-full-sb
MichaelSimons Oct 31, 2025
4014c5b
Apply suggestion from @mthalman
MichaelSimons Oct 31, 2025
ee55881
Apply suggestion from @mthalman
MichaelSimons Oct 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,6 +66,12 @@ to .NET. The following sections describe how to add/upgrade the various types of

1. If the original binaries have strong name signatures, validate the source built ones have them as well.

1. Open a PR.

1. Trigger a full source build within the VMR from your PR by adding a `/azp run source-build-reference-packages-unified-build` comment.
This will validate the new external will build without adding prebuilts.
It will also ensure the external does not contain prohibited checked-in binaries.

#### Updating an External Component to a Newer Version

1. Update the `./src/externalPackages/src/<external_repo_dir>` to the desired sha
Expand Down Expand Up @@ -94,6 +100,12 @@ to .NET. The following sections describe how to add/upgrade the various types of
1. Validate the version of the NuGet packages and binaries produced by the build.
See the contents of `./artifacts/packages/<build_configuration>/Shipping`.

1. Open a PR.

1. Trigger a full source build within the VMR from your PR by adding a `/azp run source-build-reference-packages-unified-build` comment.
This will validate the new version will build without adding prebuilts.
It will also ensure the new version does not contain prohibited checked-in binaries.

1. After the PR is merged to update a component, coordination is often needed in the darc dependency flows.
The source-build-reference-packages source may need to flow in at the same time as the cooresponding changes in product repos which take a dependency on the new component version.
Sometimes it can be easier to add the new upgraded version along side the older version and then delete the old version after all product repos have been upgraded to the new version.
Expand Down