Skip to content

chore(deps): update dependency bazelbuild/bazelisk to v1.28.1#16004

Open
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/bazelbuild-bazelisk-1.x
Open

chore(deps): update dependency bazelbuild/bazelisk to v1.28.1#16004
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/bazelbuild-bazelisk-1.x

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Feb 24, 2026

This PR contains the following updates:

Package Update Change
bazelbuild/bazelisk minor v1.27.0v1.28.1

Release Notes

bazelbuild/bazelisk (bazelbuild/bazelisk)

v1.28.1

Compare Source

Bazelisk v1.28.1 comes with a bug fix:

Bug Fixes & Improvements (Go)
  • Fix selection of wrapper scripts on Windows (#​762).

We’d like to thank our amazing contributor @​valco1994!

v1.28.0

Compare Source

Bazelisk v1.28.0 comes with a new feature and several improvements:

New Features (Go)
  • Bazelisk now supports OS/architecture-specific Bazel wrappers (#​696).
Bug Fixes & Improvements (Go)
  • Properly handle $PATH values containing a = (#​720).
  • $BAZELISK_BASE_URL: append rc suffix for release candidates (#​722).
  • Fixed handling of powershell and batch wrappers (#​732).
  • Updated completion script filename for fish shell (#​733).
  • $BAZELISK_BASE_URL: added a regression test (#​734).
  • Docs now mention installation via mise (#​739).
  • Properly detect rolling release version in a rare edge case. (#​745).
  • Improved error when completion command is not supported (#​747).
  • Report a proper exit code when Bazel is terminated by a signal and use exec for bazelisk run on Unix (#​757).
Bug Fixes & Improvements (JavaScript)
  • Wait for graceful exit of child process during shutdown (#​730).

We’d like to thank our amazing contributors @​cerisier, @​chrisirhc, @​hagl, @​jmmv, @​jwnimmer-tri, @​jylenhof, @​oxidase and @​valco1994!


Configuration

📅 Schedule: Branch creation - Monday through Friday ( * * * * 1-5 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.


This change is Reviewable

@renovate-bot renovate-bot requested a review from a team as a code owner February 24, 2026 22:18
@dpebot
Copy link

dpebot commented Feb 24, 2026

/gcbrun

@gemini-code-assist
Copy link

Summary of Changes

Hello @renovate-bot, 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 upgrades the bazelbuild/bazelisk dependency to version v1.28.1 within several Dockerfiles used for continuous integration. This update introduces new capabilities, such as OS/architecture-specific Bazel wrappers, and resolves various bugs and improves stability across different platforms, ensuring a more robust build environment.

Highlights

  • Dependency Update: The bazelbuild/bazelisk dependency has been updated from v1.27.0 to v1.28.1 across all relevant Dockerfiles.
  • New Feature: Bazelisk now includes support for OS/architecture-specific Bazel wrappers.
  • Bug Fixes & Improvements: This update incorporates fixes for wrapper script selection on Windows, improved handling of $PATH values, and enhancements for PowerShell and batch wrappers, among other general improvements.
Changelog
  • ci/cloudbuild/dockerfiles/checkers.Dockerfile
    • Updated the Bazelisk download URL to version v1.28.1.
  • ci/cloudbuild/dockerfiles/fedora-latest-bazel.Dockerfile
    • Updated the Bazelisk download URL to version v1.28.1.
  • ci/cloudbuild/dockerfiles/fedora-msan.Dockerfile
    • Updated the Bazelisk download URL to version v1.28.1.
  • ci/cloudbuild/dockerfiles/ubuntu-22.04.Dockerfile
    • Updated the Bazelisk download URL to version v1.28.1.
  • ci/cloudbuild/dockerfiles/ubuntu-24.04.Dockerfile
    • Updated the Bazelisk download URL to version v1.28.1.
Activity
  • This pull request was automatically generated by Renovate Bot to update the bazelbuild/bazelisk dependency.
  • No human activity has been recorded since its creation.
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

@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 bazelbuild/bazelisk to version v1.28.1. The changes are correct, but they highlight an area for improvement in the Dockerfiles. The bazelisk version is hardcoded in five separate files, which makes maintenance difficult. I've added a comment suggesting a refactoring to use a build argument for the version number, which would align with the repository's style guide on avoiding code duplication. This comment does not contradict any of the provided rules and is therefore kept as is.

Comment on lines +57 to 59
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
chmod +x /usr/bin/bazelisk && \
ln -s /usr/bin/bazelisk /usr/bin/bazel

Choose a reason for hiding this comment

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

medium

The bazelisk version is hardcoded and duplicated across five different Dockerfiles: checkers.Dockerfile, fedora-latest-bazel.Dockerfile, fedora-msan.Dockerfile, ubuntu-22.04.Dockerfile, and ubuntu-24.04.Dockerfile. This makes future version updates tedious and error-prone.

To improve maintainability and adhere to the project's style guide regarding code duplication, consider defining the version using a build argument at the top of each Dockerfile.

For example:

# At the top of the Dockerfile
ARG BAZELISK_VERSION=v1.28.1

...

# In the RUN command
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \
    chmod +x /usr/bin/bazelisk && \
    ln -s /usr/bin/bazelisk /usr/bin/bazel

This would make future updates much easier. While this refactoring is larger than the current change, it would be a valuable improvement.

References
  1. The repository style guide prefers to factor out duplicated code if it appears 3 or more times in non-test files. The bazelisk version is duplicated across 5 Dockerfiles. (link)

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