Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bazel_9 9.1.0 -> 9.1.1 https://github.com/bazelbuild/bazel/releases
attrpath: bazel_9
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/by-name/ba/bazel_9/package.nix b/pkgs/by-name/ba/bazel_9/package.nix
index 29838dd3bb6d..4b7d2b692d7a 100644
--- a/pkgs/by-name/ba/bazel_9/package.nix
+++ b/pkgs/by-name/ba/bazel_9/package.nix
@@ -29,7 +29,7 @@
   cctools,
   # Allow to independently override the jdks used to build and run respectively
   jdk_headless,
-  version ? "9.1.0",
+  version ? "9.1.1",
 }:
 
 let
@@ -89,7 +89,7 @@ let
 
   src = fetchzip {
     url = "https://github.com/bazelbuild/bazel/releases/download/${version}/bazel-${version}-dist.zip";
-    hash = "sha256-RbRM9HxcBij5gbd0aeArslc/IyjvycM5v7zOnaDT3cU=";
+    hash = "sha256-NwZQcycUMAzos1wLdSlwv2EjhDcPVJgQTkLT57AjFvI=";
     stripRoot = false;
   };
 

Successfully finished processing
[check][nixpkgs-review]
## `nixpkgs-review` result

Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).

Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `25c52b6c7e3f590ee59c99037c798ea69dedfc50`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>bazel_9</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/bazelbuild/bazel/releases.

meta.description for bazel_9 is: Build tool that builds code quickly and reliably

meta.homepage for bazel_9 is: https://github.com/bazelbuild/bazel/




###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/bazelbuild/bazel/releases/tag/9.1.1)

- [Compare changes on GitHub](https://github.com/bazelbuild/bazel/compare/9.1.0...9.1.1)

###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 9.1.1 with grep in /nix/store/b91wv3773x4684a6cihkf13my7wz370b-bazel-9.1.1
- found 9.1.1 in filename of file in /nix/store/b91wv3773x4684a6cihkf13my7wz370b-bazel-9.1.1

---

<details>
<summary>
<b>Rebuild report</b> (if merged into master) (click to expand)
</summary>

```
2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

bazel_9
```

</details>

<details>
<summary>
<b>Instructions to test this update</b> (click to expand)
</summary>

---

Either **download from the cache**:
```
nix-store -r /nix/store/b91wv3773x4684a6cihkf13my7wz370b-bazel-9.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nixpkgs-update-cache.nix-community.org/' \
  --option trusted-public-keys '
  nixpkgs-update-cache.nix-community.org-1:U8d6wiQecHUPJFSqHN9GSSmNkmdiFW7GW7WNAnHW0SM=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '
```
(The nixpkgs-update cache is only trusted for this store-path realization.)
For the cached 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 bazel_9 https://github.com/r-ryantm/nixpkgs/archive/25c52b6c7e3f590ee59c99037c798ea69dedfc50.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/25c52b6c7e3f590ee59c99037c798ea69dedfc50#bazel_9
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/b91wv3773x4684a6cihkf13my7wz370b-bazel-9.1.1
ls -la /nix/store/b91wv3773x4684a6cihkf13my7wz370b-bazel-9.1.1/bin
```

---

</details>
<br/>



### 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.

## `nixpkgs-review` result

Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).

Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `25c52b6c7e3f590ee59c99037c798ea69dedfc50`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>bazel_9</li>
  </ul>
</details>

---

###### Maintainer pings

cc @mboes @avdv @olebedev @groodt @aherrmann @ylecornec @boltzmannrain for [testing](https://github.com/nix-community/nixpkgs-update/blob/main/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).

> [!TIP]
> As a maintainer, if your package is located under `pkgs/by-name/*`, you can comment **`@NixOS/nixpkgs-merge-bot merge`** to automatically merge this update using the [`nixpkgs-merge-bot`](https://github.com/NixOS/nixpkgs/blob/master/ci/README.md#nixpkgs-merge-bot).
https://api.github.com/repos/NixOS/nixpkgs/pulls/527763