Set BAZELISK var to bazelisk executable path
#612
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
meteorcloudy
approved these changes
Sep 19, 2024
Member
meteorcloudy
left a comment
meteorcloudy
left a comment
There was a problem hiding this comment.
@fweikert might also want to take a look
fweikert
approved these changes
Sep 19, 2024
zemnmez-renovate-bot
added a commit
to zemn-me/monorepo
that referenced
this pull request
Sep 30, 2024
##### [`v1.22.0](https://github.com/bazelbuild/bazelisk/releases/tag/v1.22.0) 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 (bazelbuild/bazelisk#612) - `--bisect` now supports finding the first *fixing* commit by prefixing the range with `~` (bazelbuild/bazelisk#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 (bazelbuild/bazelisk#614) We’d like to thank our amazing contributors [@fmeum](https://github.com/fmeum) and [@jwnimmer-tri](https://github.com/jwnimmer-tri)!
github-merge-queue bot
pushed a commit
to zemn-me/monorepo
that referenced
this pull request
Sep 30, 2024
##### [`v1.22.0](https://github.com/bazelbuild/bazelisk/releases/tag/v1.22.0) 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 (bazelbuild/bazelisk#612) - `--bisect` now supports finding the first *fixing* commit by prefixing the range with `~` (bazelbuild/bazelisk#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 (bazelbuild/bazelisk#614) We’d like to thank our amazing contributors [@fmeum](https://github.com/fmeum) and [@jwnimmer-tri](https://github.com/jwnimmer-tri)!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This can be useful for scripts that want to know if they are running under Bazelisk and can also be used to run specific Bazel versions from within a Bazel run, e.g. to generate version-specific test data.