chore(deps): update dependency @bazel/bazelisk to ^1.25.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@bazel/bazelisk	^1.19.0 -> ^1.25.0

---

Release Notes

bazelbuild/bazelisk (@​bazel/bazelisk)

v1.25.0

Compare Source

Bazelisk v1.25.0 comes with several improvements:

New Features (Python)

• Added support for .bazeliskrc files (https://github.com/bazelbuild/bazelisk/pull/494).

Bug Fixes & Improvements (Go)

• Made it easier for other tools to use Bazelisk's core logic to locate (and download) Bazel binaries (https://github.com/bazelbuild/bazelisk/pull/635).
• Fixed errors when multiple Bazelisk instances were running in parallel (https://github.com/bazelbuild/bazelisk/pull/638).
• Improved signal handling (https://github.com/bazelbuild/bazelisk/pull/642).
• bazelisk version now also prints the Bazelisk version even if startup flags are set (https://github.com/bazelbuild/bazelisk/pull/646).

We’d like to thank our amazing contributors @​hauserx, @​jwnimmer-tri and @​shs96c!

v1.24.1

Compare Source

Bazelisk v1.24.1 is a patch release with some minor fixes:

Bug Fixes & Improvements

• bisect now accepts Bazel release branch names (https://github.com/bazelbuild/bazelisk/pull/633).
• Improved error message when LTS binaries are missing (https://github.com/bazelbuild/bazelisk/pull/639).
• Fixed a performance regression caused by too many unnecessary HTTP requests, which was introduced in v1.24.0 (https://github.com/bazelbuild/bazelisk/pull/641).

We’d like to thank our amazing users & contributors!

v1.24.0

Compare Source

Bazelisk v1.24.0 comes with a new feature:

New Features (Go)

• Implemented support for a new wildcard version identifier: Users may now specify a version like 7.* that refers to the latest release or candidate from the given LTS track. Please note that this is different from the existing 7.x identifier which only matches releases, but not candidates (https://github.com/bazelbuild/bazelisk/pull/636).

We’d like to thank our amazing users & contributors!

Known issue: https://github.com/bazelbuild/bazelisk/issues/640

v1.23.0

Compare Source

Bazelisk v1.23.0 comes with several improvements related to downloads:

Bug Fixes & Improvements

• Improved download error messages (https://github.com/bazelbuild/bazelisk/pull/624)
• Fixed INTERNAL_ERROR problems caused by improper handling of HTTP responses during retries (https://github.com/bazelbuild/bazelisk/pull/627)

We’d like to thank our amazing contributors @​jjmaestro and @​jwnimmer-tri!

v1.22.1

Compare Source

Bazelisk v1.22.1 is a patch release with the following changes:

Bug Fixes & Improvements

• Multiple instances of Bazelisk can now run concurrently without causing problems (https://github.com/bazelbuild/bazelisk/pull/616).

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

v1.22.0

Compare Source

Bazelisk v1.22.0 comes with several significant changes:

New Features (Go)

• Bazelisk sets the BAZELISK env variable so that scripts can detect whether they're running under Bazelisk (https://github.com/bazelbuild/bazelisk/pull/612)
• --bisect now supports finding the first fixing commit by prefixing the range with ~ (https://github.com/bazelbuild/bazelisk/pull/613)

Removed Features (Go)

• Removed support for last_downstream_green since the downstream pipeline stopped producing green commits some time ago.

Bug Fixes & Improvements

• Improved last_green support (https://github.com/bazelbuild/bazelisk/pull/614)

We’d like to thank our amazing contributors @​fmeum and @​jwnimmer-tri!

v1.21.0

Compare Source

Bazelisk v1.21.0 comes with several significant changes:

New Features (Go)

• Users can set an OS-specific Bazelisk home directory, e.g. via BAZELISK_HOME_WINDOWS (https://github.com/bazelbuild/bazelisk/pull/474)
• BAZELISK_WRAPPER_DIRECTORY allows users to specify paths other than the default tools/bazel location (https://github.com/bazelbuild/bazelisk/pull/567)
• BAZELISK_HOME: Environment variables as well as the tilde sign are now properly expanded (https://github.com/bazelbuild/bazelisk/pull/587)
• Bazelisk can fetch Linux ARM64 Bazel binaries built for commits (https://github.com/bazelbuild/bazelisk/pull/604)

Bug Fixes & Improvements

• The Python version properly handles empty lines in .bazelversion files (https://github.com/bazelbuild/bazelisk/pull/576)

We’d like to thank our amazing contributors @​albertocavalcante, @​API92, @​jwnimmer-tri, @​keith and @​mzapotoczny!

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

[gcf-merge-on-green]

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.