fix(dependabot): add support for cargo and pub registries#4853
Merged
hyperupcall merged 3 commits intoSchemaStore:masterfrom Jul 17, 2025
Merged
fix(dependabot): add support for cargo and pub registries#4853hyperupcall merged 3 commits intoSchemaStore:masterfrom
hyperupcall merged 3 commits intoSchemaStore:masterfrom
Conversation
Contributor
|
Thanks for the PR! This section of the codebase is owned by @madskristensen and |
Member
|
Thanks |
This file contains hidden or 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
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.
GitHub supports 2 (new) registires in Dependabot custom registry yaml configuration.
There were missing from the current V2 schema (all schemas >=V2 support these ones)
According to this documentation
EDIT:
GitHub docs seem to have a typo.
I'm using the custom pub registry, but GitHub returns an error if setting
pub-registrylike in the docs, instead ofpub-repository.Here's the sample error:
Therefore, I can confirm regarding the error, and local testing, that it should be
pub-repository.