fix(Renovate): Prefer GitHub releases to tags #348
Merged
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.
This repository itself, GitHub-hosted runner images, asdf, and the .NET SDK all publish GitHub releases in addition to tags. Use the releases as the datasource so that bumps can't precede the crafting of release notes and to skip versions that are tagged but never released. Some projects signal that a tagged version was bad by not creating a release for them. Continue using GitHub tags to bump the dependencies that don't create GitHub releases, namely Python and the Yarn licenses plugin.