Configure Dependabot to use public Nuget registry #404
Conversation
This file contains 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
keyuxuan
approved these changes
Aug 29, 2024
Haard30
approved these changes
Aug 29, 2024
reillysiemens
approved these changes
Aug 29, 2024
mijpeterson
added a commit
that referenced
this pull request
Aug 29, 2024
This reverts commit a119bb5.
mijpeterson
added a commit
that referenced
this pull request
Aug 29, 2024
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.
In an attempt to get continuous version and security updates from dependabot, I want to experiment with having it explicitly target the public nuget feed.
Because our nuget.config file points to a private nuget registry, dependabot is unable to successfully run against our Nuget packages. This is visible through the most recent dependabot update logs: https://github.com/AzureAD/microsoft-authentication-cli/network/updates/875662189.
You can configure dependabot.yml with credentials to access a private registry, but you need to provide it with a static token defined in the repo secrets. Since long-lived PATs are being phased out as part of SFI, we're unable to do so. Dependabot also does not have a way to programmatically retrieve a short-lived OAuth token.
My thinking is that if you can configure dependabot to point to a private registry, perhaps we can configure it to point to the public nuget registry?
I have not found a way to test dependabot against a non-default branch, so my current plan is to experiment with it in main and see if it works. If it doesn't work as expected, I'll be making subsequent PRs to either patch it some more or revert the change.