Skip to content

chore(deps): update dependency bazelbuild/bazelisk to v1.29.0#16123

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

chore(deps): update dependency bazelbuild/bazelisk to v1.29.0#16123
renovate-bot wants to merge 1 commit into
googleapis:mainfrom
renovate-bot:renovate/bazelbuild-bazelisk-1.x

Conversation

@renovate-bot
Copy link
Copy Markdown
Contributor

This PR contains the following updates:

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

Release Notes

bazelbuild/bazelisk (bazelbuild/bazelisk)

v1.29.0

Compare Source

Bazelisk v1.29.0 comes with new features and several improvements:

New Features (Go Binary)

  • Official Bazel releases will be authenticated via an embedded verification key (#​192).
  • Bazelisk now supports the bazeliskVersion command so that users can see the Bazelisk version without having to download/run Bazel (#​763).

New Features (Go Library)

  • Callers can now capture stderr via an io.Writer (#​751).

Bug Fixes & Improvements (Go)

  • On non-Windows machines Bazelisk will be run via exec instead of in a subprocess (#​566).
  • Bazelisk releases now come with sha256 checksums (#​770).

We’d like to thank our amazing contributors @​aaron-skydio, @​isakstenstrom, @​PiotrSikora, @​sitaktif and @​valco1994!


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Monday through Friday (* * * * 1-5)
  • 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.

@renovate-bot renovate-bot requested a review from a team as a code owner May 27, 2026 17:33
@dpebot
Copy link
Copy Markdown
Collaborator

dpebot commented May 27, 2026

/gcbrun

Copy link
Copy Markdown

@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 Bazelisk version from v1.28.1 to v1.29.0 across five Dockerfiles. The reviewer suggests using an ARG instruction to define the Bazelisk version to improve maintainability and reduce code duplication, as the version string is currently repeated across multiple files.

mdformat-footnote==0.1.1

RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.29.0/bazelisk-linux-${ARCH}" && \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve maintainability and avoid duplicating the version string across multiple Dockerfiles, define the Bazelisk version using an ARG instruction.

ARG BAZELISK_VERSION=1.29.0
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \\
References
  1. In Dockerfiles, use ARG to define version strings that are duplicated across multiple files to improve maintainability.

ENV PATH=${CLOUD_SDK_LOCATION}/bin:${PATH}

RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.29.0/bazelisk-linux-${ARCH}" && \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve maintainability and avoid duplicating the version string across multiple Dockerfiles, define the Bazelisk version using an ARG instruction.

ARG BAZELISK_VERSION=1.29.0
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \\
References
  1. In Dockerfiles, use ARG to define version strings that are duplicated across multiple files to improve maintainability.

ENV PATH=${CLOUD_SDK_LOCATION}/bin:${PATH}

RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.29.0/bazelisk-linux-${ARCH}" && \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve maintainability and avoid duplicating the version string across multiple Dockerfiles, define the Bazelisk version using an ARG instruction.

ARG BAZELISK_VERSION=1.29.0
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \\
References
  1. In Dockerfiles, use ARG to define version strings that are duplicated across multiple files to improve maintainability.

ENV PATH=${CLOUD_SDK_LOCATION}/bin:${PATH}

RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.29.0/bazelisk-linux-${ARCH}" && \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve maintainability and avoid duplicating the version string across multiple Dockerfiles, define the Bazelisk version using an ARG instruction.

ARG BAZELISK_VERSION=1.29.0
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \\
References
  1. In Dockerfiles, use ARG to define version strings that are duplicated across multiple files to improve maintainability.

ENV PATH=${CLOUD_SDK_LOCATION}/bin:${PATH}

RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.28.1/bazelisk-linux-${ARCH}" && \
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v1.29.0/bazelisk-linux-${ARCH}" && \
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

To improve maintainability and avoid duplicating the version string across multiple Dockerfiles, define the Bazelisk version using an ARG instruction.

ARG BAZELISK_VERSION=1.29.0
RUN curl -o /usr/bin/bazelisk -sSL "https://github.com/bazelbuild/bazelisk/releases/download/v${BAZELISK_VERSION}/bazelisk-linux-${ARCH}" && \\
References
  1. In Dockerfiles, use ARG to define version strings that are duplicated across multiple files to improve maintainability.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 27, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.71%. Comparing base (00f057d) to head (41a7d2a).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #16123   +/-   ##
=======================================
  Coverage   92.71%   92.71%           
=======================================
  Files        2353     2353           
  Lines      219451   219451           
=======================================
+ Hits       203454   203470   +16     
+ Misses      15997    15981   -16     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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