Skip to content

Update instructions for adding new repo support to update-dependencies #6811

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
lbussell merged 1 commit into from
Nov 12, 2025
Merged

Update instructions for adding new repo support to update-dependencies #6811

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 10 additions & 3 deletions eng/update-dependencies/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -33,9 +33,16 @@ removal tracked by [this GitHub issue](https://github.com/dotnet/docker-tools/is

### .NET dependencies

If the .NET dependency can be resolved from a BAR (build asset registry) build,
you may be able to add support to the [BuildUpdaterService](./BuildUpdaterService.cs),
or adapt its code for a similar use.
To add support for new .NET repos to the `from-build` and `from-channel`
commands:

- Add the new repo to the [`BuildRepo`](./BuildRepo.cs) enum.
- Update the [GetBuildRepo()](./BuildExtensions.cs) extension method to support
the new enum value.
- Implement a new [`IBuildUpdaterService`](./IBuildUpdaterService.cs), using
existing implementations as a reference.
- Register a new keyed singleton in [Program.cs](./Program.cs) using the new
repo enum value as the key.

If the dependency can be resolved from a pipeline artifact, GitHub release,
static file, or something similar, then you may be able to treat it like an
Expand Down
Loading