Skip to content

Conversation

@mmoll
Copy link

@mmoll mmoll commented Feb 12, 2026

No description provided.

@google-cla
Copy link

google-cla bot commented Feb 12, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@mmoll mmoll mentioned this pull request Feb 12, 2026
3 tasks
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @mmoll, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on upgrading the rules_distroless dependency to its latest version. This core update necessitated a cascade of changes across the Bazel module lock file, bringing various other transitive dependencies and their associated hashes up to date. A notable change within the lock file is the shift in toolchain management from tar.bzl to yq.bzl, reflecting an evolution in how external tools are integrated into the build system.

Highlights

  • Dependency Update: The rules_distroless dependency has been updated from version 0.5.3 to 0.6.2 in MODULE.bazel.
  • Lock File Updates: The MODULE.bazel.lock file has been extensively updated to reflect new hashes and versions for several transitive dependencies, including bazel_features, bazel_lib, bazel_skylib, gawk, rules_cc, tar.bzl, and yq.bzl.
  • Toolchain Migration: The lock file indicates a migration from tar.bzl based toolchains (bsd_tar_toolchains) to yq.bzl based toolchains (yq_toolchains), including new platform-specific yq_platform_repo entries.
  • Module Extension Digests: Several bzlTransitiveDigest values for module extensions like busybox, version, and cu_nr have been updated in the lock file.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • MODULE.bazel
    • Updated rules_distroless version from 0.5.3 to 0.6.2.
  • MODULE.bazel.lock
    • Updated bazel_features references to version 1.34.0.
    • Added new entries for bazel_lib versions 3.0.0-beta.1 and 3.0.0-rc.0.
    • Updated bazel_skylib references to version 1.8.2.
    • Updated gawk references to version 5.3.2.bcr.3.
    • Updated rules_cc references to version 0.2.4.
    • Updated rules_distroless references to version 0.6.2.
    • Updated tar.bzl references to version 0.6.0.
    • Updated yq.bzl references to version 0.3.1.
    • Modified dependency array for rules_distroless~ to reference bazel_lib instead of aspect_bazel_lib.
    • Replaced tar.bzl toolchain definitions with yq.bzl toolchain definitions, including platform-specific yq_platform_repo entries.
    • Updated bzlTransitiveDigest values for busybox, version, and cu_nr module extensions.
Activity
  • No human activity has been recorded on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the rules_distroless dependency to version 0.6.2. The changes in MODULE.bazel and the corresponding updates in MODULE.bazel.lock are consistent with this dependency bump. I have one suggestion to also update the version of a direct dependency that was transitively updated, to improve the clarity and maintainability of your MODULE.bazel file.

@mmoll mmoll force-pushed the rules_distroless_0.6.2 branch from b6f1e51 to 5666e70 Compare February 12, 2026 17:34
@loosebazooka
Copy link
Member

dunno what rules_distroless is doing here, but none of these tests are gonna pass because gawk-5.3.2.tar.xz is not obtainable form the mirror right now

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.

2 participants