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

Implement Bazel module lockfile support #25557

Open
rarkins opened this issue Nov 2, 2023 Discussed in #25532 · 0 comments
Open

Implement Bazel module lockfile support #25557

rarkins opened this issue Nov 2, 2023 Discussed in #25532 · 0 comments
Labels
manager:bazel Bazel WORKSPACE files priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)

Comments

@rarkins
Copy link
Collaborator

rarkins commented Nov 2, 2023

Discussed in #25532

Originally posted by cgrindel November 1, 2023

Tell us more.

Requirements

  • Read the .bazelversion. Ensure that it is 6.4.0 or later.
  • Read the bazelrc files looking for --lockfile_mode. If not found, it is assumed to be update.
  • Lockfile Mode
    • update: update the lockfile.
    • error: do not update the lockfile. NOTE: It is unclear why one would configure Renovate to update Bazel and have their lockfile mode be error.
    • off: do not update the lockfile.
  • If a lockfile update is warranted, execute bazel mod deps.
  • Need to ensure that bazelisk is installed on the platforms that execute Renovate (e.g., Docker images).

Related Links

@rarkins rarkins added type:feature Feature (new functionality) priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others manager:bazel Bazel WORKSPACE files labels Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
manager:bazel Bazel WORKSPACE files priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

1 participant