igir 2.2.0 -> 2.2.1 https://github.com/emmercm/igir/releases
attrpath: igir
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] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] Replacing npmDepsHash with sha256-yVo2ZKu2lEOYG12Gk5GQXamprkP5jEyKlSTZdPjNWQM=
[npmDepsVersion] Finished updating NPM deps version and replacing hashes
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/tools/games/igir/default.nix b/pkgs/tools/games/igir/default.nix
index 6776f894dd70..4f4cf048a659 100644
--- a/pkgs/tools/games/igir/default.nix
+++ b/pkgs/tools/games/igir/default.nix
@@ -5,16 +5,16 @@
 
 buildNpmPackage rec {
   pname = "igir";
-  version = "2.2.0";
+  version = "2.2.1";
 
   src = fetchFromGitHub {
     owner = "emmercm";
     repo = "igir";
     rev = "v${version}";
-    hash = "sha256-RHMsLiet3O/4aYLKWtxr1oJDU6sy5kHxr422AUqLzMA=";
+    hash = "sha256-MlLnnwlqFkzSZi+6OGS/ZPYRPjV7CY/piFvilwhhR9A=";
   };
 
-  npmDepsHash = "sha256-MvXhSSqHHI3Ofgx+EnKwR5LuHl33h6sjTZ+ErBfjb6s=";
+  npmDepsHash = "sha256-yVo2ZKu2lEOYG12Gk5GQXamprkP5jEyKlSTZdPjNWQM=";
 
   # I have no clue why I have to do this
   postPatch = ''

Successfully finished processing
cachix "/nix/store/h19dydhpcch8jjpdqpsv08wnyx721p24-igir-2.2.1"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>igir</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/emmercm/igir/releases.


meta.description for igir is: A video game ROM collection manager to help filter, sort, patch, archive, and report on collections on any OS

meta.homepage for igir is: https://igir.io




###### Updates performed
- NPM version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/emmercm/igir/releases/tag/v2.2.1)

- [Compare changes on GitHub](https://github.com/emmercm/igir/compare/v2.2.0...v2.2.1)

###### Impact

<b>Checks done</b>

---

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

---

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

```
1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
igir
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/h19dydhpcch8jjpdqpsv08wnyx721p24-igir-2.2.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 igir https://github.com/r-ryantm/nixpkgs/archive/3053795ff3c8dcced0f96008afc66dc56755aaed.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/3053795ff3c8dcced0f96008afc66dc56755aaed#igir
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/h19dydhpcch8jjpdqpsv08wnyx721p24-igir-2.2.1
ls -la /nix/store/h19dydhpcch8jjpdqpsv08wnyx721p24-igir-2.2.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.

Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>igir</li>
  </ul>
</details>

---

###### Maintainer pings

cc @TheBrainScrambler 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/279111