bazel-gazelle 0.31.0 -> 0.31.1 https://github.com/bazelbuild/bazel-gazelle/releases
attrpath: bazel-gazelle
Checking auto update branch...
No auto update branch exists
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Found old vendorHash = null
[golangModuleVersion] Set vendorHash to null
[golangModuleVersion] Finished updating vendorHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript

[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/development/tools/bazel-gazelle/default.nix b/pkgs/development/tools/bazel-gazelle/default.nix
index e31ddd0b376..93636af5022 100644
--- a/pkgs/development/tools/bazel-gazelle/default.nix
+++ b/pkgs/development/tools/bazel-gazelle/default.nix
@@ -5,13 +5,13 @@
 
 buildGoModule rec {
   pname = "bazel-gazelle";
-  version = "0.31.0";
+  version = "0.31.1";
 
   src = fetchFromGitHub {
     owner = "bazelbuild";
     repo = pname;
     rev = "v${version}";
-    sha256 = "sha256-Y1otQcGtG7jIJE5G0DET8bFRVL6AEG0r98X5PufT7Lw=";
+    sha256 = "sha256-avc92qQS2d8MiQVRUYEiMOlsfgQFJ6HZG01rmZeC9Fo=";
   };
 
   vendorHash = null;

Successfully finished processing
cachix "/nix/store/n55cxhpmxr4bpi64n564vq1a55b2m5dz-bazel-gazelle-0.31.1"
[check][nixpkgs-review]
[check][nixpkgs-review] took longer than 45m and timed out
nixpkgs-review took longer than 45m and timed out
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/bazelbuild/bazel-gazelle/releases.


meta.description for bazel-gazelle is: Gazelle is a Bazel build file generator for Bazel projects. It natively
supports Go and protobuf, and it may be extended to support new languages
and custom rule sets.

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




###### Updates performed
- Golang update

###### To inspect upstream changes

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

- [Compare changes on GitHub](https://github.com/bazelbuild/bazel-gazelle/compare/v0.31.0...v0.31.1)

###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 0.31.1 in filename of file in /nix/store/n55cxhpmxr4bpi64n564vq1a55b2m5dz-bazel-gazelle-0.31.1

---

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

```
3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
bazel-gazelle
envoy
pomerium
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/n55cxhpmxr4bpi64n564vq1a55b2m5dz-bazel-gazelle-0.31.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 bazel-gazelle https://github.com/r-ryantm/nixpkgs/archive/79dd7b033a835fa64c35a2152cb4351ef94c54e3.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/n55cxhpmxr4bpi64n564vq1a55b2m5dz-bazel-gazelle-0.31.1
ls -la /nix/store/n55cxhpmxr4bpi64n564vq1a55b2m5dz-bazel-gazelle-0.31.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 took longer than 45m and timed out

---

###### Maintainer pings

cc @kalbasit 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).
https://api.github.com/repos/NixOS/nixpkgs/pulls/239859