fix: Only use GitHub releases to update Bazelisk #29847
Merged
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
mark-thm
changed the title
rarkins
requested changes
Jun 25, 2024
rarkins
approved these changes
Jun 25, 2024
|
🎉 This PR is included in version 37.417.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Changes
Change Bazelisk to use GitHub Releases datasource instead of GitHub Tags datasource.
Context
Bazel's release process is to first create a tag, and then only to create a GitHub release once all artifacts have been built and are ready/available. The GitHub tag will exist before the real Bazel release artifacts are available, which causes Renovate to create PRs that may fail or only partially succed.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: