-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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.
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
feat: add bazel
datasource
#21733
feat: add bazel
datasource
#21733
Conversation
lib/modules/datasource/bazel-registry/__snapshots__/index.spec.ts.snap
Outdated
Show resolved
Hide resolved
@zharinov would you recommend zod validation be added? |
Oh yes, schema+transform should work great here |
lib/modules/datasource/bazel-registry/__fixtures__/metadata-no-yanked-versions.json
Outdated
Show resolved
Hide resolved
bazel-registry
datasourcebazel
datasource
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise LGTM
returned in ReleaseResult.
Please do not force push changes. https://github.com/renovatebot/renovate/blob/main/.github/contributing.md#do-not-force-push-to-your-pull-request-branch |
@secustor Sorry. I thought that rule was regarding updating a commit and force pushing. How do you prefer that I bring in the latest changes from |
@secustor I just re-read the passage. I will use the 'Update branch' button. Again, sorry about that. |
🎉 This PR is included in version 35.60.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Changes
Add
bazel-registry
datasource.Context
Related to #13658.
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: