Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: explo 1.1.3 -> 1.2.0 https://github.com/LumePart/Explo/releases
attrpath: explo
Checking auto update branch...
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] No cargoHash found
[golangModuleVersion] 
[golangModuleVersion] skipping because derivation has updateScript
[npmDepsVersion] 
[npmDepsVersion] skipping because derivation has updateScript
[updateScript] 
[updateScript] Success
[updateScript] this derivation will be built:
  /nix/store/ki95rbmx0k35dwbfaiidjlb0mb849iah-packages.json.drv
building '/nix/store/ki95rbmx0k35dwbfaiidjlb0mb849iah-packages.json.drv'...
structuredAttrs is enabled

Going to be running update for following packages:
 - explo-1.1.3

Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
 - explo-1.1.3: UPDATING ...
 - explo-1.1.3: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/ex/explo/package.nix b/pkgs/by-name/ex/explo/package.nix
index 0682ccc4fecb..3101a6e14b7f 100644
--- a/pkgs/by-name/ex/explo/package.nix
+++ b/pkgs/by-name/ex/explo/package.nix
@@ -9,7 +9,7 @@
 
 buildGoModule (finalAttrs: {
   pname = "explo";
-  version = "1.1.3";
+  version = "1.2.0";
 
   strictDeps = true;
   __structuredAttrs = true;
@@ -18,7 +18,7 @@ buildGoModule (finalAttrs: {
     owner = "LumePart";
     repo = "Explo";
     tag = "v${finalAttrs.version}";
-    hash = "sha256-Wq5oU5AVgBYN3j/m7T07ZI16RF11orysXqjPbYKVd98=";
+    hash = "sha256-T0EYPiidK/qUaCCKePDT8KIbMnu3j7Z3ADmgtuhUb/o=";
   };
 
   webui = buildNpmPackage {

No auto update branch exists
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: `49ebb76cde1a36f6a3fddf04610566a2f9bee691`

---
### `x86_64-linux`
<details>
  <summary>✅ 1 package built:</summary>
  <ul>
    <li>explo</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 passthru.updateScript.

meta.description for explo is: Spotify's "Discover Weekly" for self-hosted music systems

meta.homepage for explo is: https://github.com/LumePart/Explo/

meta.changelog for explo is: https://github.com/LumePart/Explo/releases/tag/v1.2.0


###### Updates performed
- Ran passthru.UpdateScript

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

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

---

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

```
8 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

explo
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/k43x6vy7gwbf45bdaxyj3zvj1lkpsy8i-explo-1.2.0 \
  --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 explo https://github.com/r-ryantm/nixpkgs/archive/49ebb76cde1a36f6a3fddf04610566a2f9bee691.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/49ebb76cde1a36f6a3fddf04610566a2f9bee691#explo
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/k43x6vy7gwbf45bdaxyj3zvj1lkpsy8i-explo-1.2.0
ls -la /nix/store/k43x6vy7gwbf45bdaxyj3zvj1lkpsy8i-explo-1.2.0/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: `49ebb76cde1a36f6a3fddf04610566a2f9bee691`

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

---

###### Maintainer pings

cc @Lilacious @arunoruto 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/563366