Skip to content
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

Introduce Bazel Steward - a tool for keeping dependencies up to date in Bazel #553

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

lukaszwawrzyk
Copy link

Hello everyone,

As one of developers I am submitting this pull request to introduce our new tool for Bazel repositories. Bazel Steward simplifies the process of checking and updating dependencies in your Bazel projects, making it more efficient to keep them up-to-date.
We hope that this tool will be useful to the Bazel community, and we look forward to your feedback.

This pull request integrates Bazel Steward through Github Actions which is currently the easiest way to do this. It will run every day at 12 and create new PRs or resolve conflicts on existing if necessary. You can preview how it looks in a fork that I used to test it. For more details, you can check the project readme.

Bazel Steward is able to correctly update all your maven dependencies and version of Bazel itself. Support for updating rules works in many cases, but we are still working on it to make it more robust. In order to make it work.

We hope that Bazel Steward will make it easier for you to manage dependencies. If you encounter any issues or have any feedback, please don't hesitate to reach out to us. Thank you!


Changes:

  • added GitHub Action Workflow for Bazel Steward
  • Made skylib url explicit - so that Bazel Steward can replace it (maintainers of skylib changed artifact naming scheme and it is not enough to just replace the version)
  • updated rules_jvm_external to 5.2. Version 4.0+ is required for Bazel Steward to work with Maven dependencies. Also note that you had your rules_jvm_external defined twice (once in a function and once explicitly), now it is defined once. I put it in the WORKSPACE file, because otherwise Bazel Steward is not able to detect it. We plan to support this scenario in the future
  • Excluded bazel-steward.yaml to .gitignore. It will make your life easier if you choose to configure Bazel Steward further

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant