Tags: bazelbuild/bazelisk
Tags
Bump github.com/hashicorp/go-version from 1.7.0 to 1.9.0 (#782) Bumps [github.com/hashicorp/go-version](https://github.com/hashicorp/go-version) from 1.7.0 to 1.9.0. - [Release notes](https://github.com/hashicorp/go-version/releases) - [Changelog](https://github.com/hashicorp/go-version/blob/main/CHANGELOG.md) - [Commits](hashicorp/go-version@v1.7.0...v1.9.0) --- updated-dependencies: - dependency-name: github.com/hashicorp/go-version dependency-version: 1.9.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Florian Weikert <fwe@google.com>
Fix wrappers issues in Bazelisk 1.28.0 on Windows (#762) * Rework wrappers probation order according to #761: * probe tools/bazel.exe on Windows after platform-specific executables and before Windows-specific scripts * probe tools/bazel on Windows with lowest priority (for backward compatibility only) Update core_test.go and README.md to reflect the changes. * Bazel 8.4.2 is absent on https://downloads.sourceforge.net/project/bazel.mirror, use Bazel 8.5.1 instead in the test `test_path_is_consistent_regardless_of_base_url` from bazelisk_test.sh
Report a proper exit code when Bazel is terminated by signal and use … …`exec` on Unix in the case of `bazelisk run` (#757) * Better handle Bazel process termination caused by signals on POSIX-compatible systems * Use `exec` for running bazel on Unix instead of starting it as a child process in the case of `run` command Fixes #512 and #556
Bump golang.org/x/term from 0.32.0 to 0.33.0 (#712) Bumps [golang.org/x/term](https://github.com/golang/term) from 0.32.0 to 0.33.0. - [Commits](golang/term@v0.32.0...v0.33.0) --- updated-dependencies: - dependency-name: golang.org/x/term dependency-version: 0.33.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Print Bazelisk version when startup flags are set. (#646) When invoking Bazelisk with the `version` command, the output should always start with the Bazelisk version followed by the output of `bazel version`. However, previously this was not the case when startup flags were set, e.g. when calling `bazelisk --nosystem_rc version`.
Avoid unnecessary HTTP requests for latest/last_rc (#641) * Avoid unnecessary HTTP requests for latest/last_rc The refactoring in #631 introduced a severe performance regression: With latest and last_rc the code traversed *all* GCS buckets for *every* existing Bazel version. Since we send one HTTP request per bucket, this behavior led to a significant increase in HTTP requests ( >140 instead of 2-3 requests). This commit restores the previous, correct behavior: Traversal will be stopped as soon as a matching version has been found. Moreover, this commit adds a test to prevent similar regressions in the future. Fixes #640 Drive-by fix: Replaced \"%s\" with %q. * Apply minimal indentation principle
feat: improve httputil error messages (#624) * add attempt count to the timeout error message so it's clear the timeout is due to the total time accumulated during retries. * add lastFailure to the timeout error message so we can get a clear reason for the retries (or, at the very least, the last retry). Otherwise, the error message obscures the real reason(s) for the retries and potentially misleads users into thinking that the errors could be e.g. network related (more typical of a timeout) rather than other types of errors (e.g. "tls: failed to verify certificate", etc.)
PreviousNext