2022-11-03T23:01:35 bazelisk 1.14.0 -> 1.14.1 https://repology.org/metapackage/bazelisk/versions 2022-11-03T23:01:38 attrpath: bazelisk 2022-11-03T23:01:38 Checking auto update branch... 2022-11-03T23:01:38 No auto update branch exists 2022-11-03T23:01:43 [version] 2022-11-03T23:01:43 [version] generic version rewriter does not support multiple hashes 2022-11-03T23:01:43 [rustCrateVersion] 2022-11-03T23:01:43 [rustCrateVersion] No cargoSha256 found 2022-11-03T23:01:43 [golangModuleVersion] 2022-11-03T23:01:46 [golangModuleVersion] Found old vendorSha256 = sha256-JJdFecRjPVmpYjDmz+ZBDmyT3Vj41An3BXvI2JzisIg= 2022-11-03T23:01:52 [golangModuleVersion] Replaced vendorSha256 with sha256-JJdFecRjPVmpYjDmz+ZBDmyT3Vj41An3BXvI2JzisIg= 2022-11-03T23:02:03 [golangModuleVersion] Finished updating vendorSha256 2022-11-03T23:02:03 [updateScript] 2022-11-03T23:02:03 [updateScript] skipping because derivation has no updateScript 2022-11-03T23:02:03 2022-11-03T23:02:03 [quotedUrls] 2022-11-03T23:02:03 [quotedUrls] nothing found to replace 2022-11-03T23:02:03 Diff after rewrites: diff --git a/pkgs/development/tools/bazelisk/default.nix b/pkgs/development/tools/bazelisk/default.nix index 5c5e7c2d530..ee32e97cc77 100644 --- a/pkgs/development/tools/bazelisk/default.nix +++ b/pkgs/development/tools/bazelisk/default.nix @@ -2,13 +2,13 @@ buildGoModule rec { pname = "bazelisk"; - version = "1.14.0"; + version = "1.14.1"; src = fetchFromGitHub { owner = "bazelbuild"; repo = pname; rev = "v${version}"; - sha256 = "sha256-y3DVU2xHYZGUqf+kXhBDpTHACloqOXiMFY9bWU/QfOg="; + sha256 = "sha256-keLcq2K6LJXrCbgvkSUVtkaVo+Mt6WKNxw+2k01C/4U="; }; vendorSha256 = "sha256-JJdFecRjPVmpYjDmz+ZBDmyT3Vj41An3BXvI2JzisIg="; 2022-11-03T23:03:45 Successfully finished processing 2022-11-03T23:03:45 cachix "/nix/store/rq7b5dyfwg7x0d2a4f2yql6lmacid0vx-bazelisk-1.14.1" 2022-11-03T23:03:50 [check][nixpkgs-review] 2022-11-03T23:06:55 Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
2022-11-03T23:06:59 Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/metapackage/bazelisk/versions. meta.description for bazelisk is: "A user-friendly launcher for Bazel" meta.homepage for bazelisk is: "https://github.com/bazelbuild/bazelisk" meta.changelog for bazelisk is: "" ###### Updates performed - Golang update ###### To inspect upstream changes - [Compare changes on GitHub](https://github.com/bazelbuild/bazelisk/compare/v1.14.0...v1.14.1) ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.14.1 in filename of file in /nix/store/rq7b5dyfwg7x0d2a4f2yql6lmacid0vx-bazelisk-1.14.1 ---
Rebuild report (if merged into master) (click to expand) ``` 1 total rebuild path(s) 1 package rebuild(s) First fifty rebuilds by attrpath bazelisk ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/rq7b5dyfwg7x0d2a4f2yql6lmacid0vx-bazelisk-1.14.1 \ --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \ --option trusted-public-keys ' nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs= cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY= ' ``` (The Cachix cache is only trusted for this store-path realization.) For the Cachix download to work, your user must be in the `trusted-users` list or you can use `sudo` since root is effectively trusted. Or, **build yourself**: ``` nix-build -A bazelisk https://github.com/r-ryantm/nixpkgs/archive/75d1bc2509eadc3a70e53705ddcbbf735aa3945e.tar.gz ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/rq7b5dyfwg7x0d2a4f2yql6lmacid0vx-bazelisk-1.14.1 ls -la /nix/store/rq7b5dyfwg7x0d2a4f2yql6lmacid0vx-bazelisk-1.14.1/bin ``` ---

### Pre-merge build results We have automatically built all packages that will get rebuilt due to this change. This gives evidence on whether the upgrade will break dependent packages. Note sometimes packages show up as _failed to build_ independent of the change, simply because they are already broken on the target branch. Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package built:
--- ###### Maintainer pings cc @elasticdog for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do). 2022-11-03T23:07:00 https://api.github.com/repos/NixOS/nixpkgs/pulls/199421