frigate 0 -> 1
attrpath: frigate
Checking auto update branch...
[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] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] 
Going to be running update for following packages:
 - frigate-0.13.1

Press Enter key to continue...
Running update for:
 - frigate-0.13.1: UPDATING ...
 - frigate-0.13.1: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/applications/video/frigate/default.nix b/pkgs/applications/video/frigate/default.nix
index d6437d09f421..9aee25c46ce5 100644
--- a/pkgs/applications/video/frigate/default.nix
+++ b/pkgs/applications/video/frigate/default.nix
@@ -9,14 +9,14 @@
 }:
 
 let
-  version = "0.13.1";
+  version = "0.13.2";
 
   src = fetchFromGitHub {
     #name = "frigate-${version}-source";
     owner = "blakeblackshear";
     repo = "frigate";
     rev = "refs/tags/v${version}";
-    hash = "sha256-2J7DhnYDX9ubbsk0qhji/vIKDouy9IqQztzbdPj2kxo=";
+    hash = "sha256-NVT7yaJkVA7b7GL0S0fHjNneBzhjCru56qY1Q4sTVcE=";
   };
 
   frigate-web = callPackage ./web.nix {

No auto update branch exists
Successfully finished processing
cachix "/nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2"
[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>frigate</li>
  </ul>
</details>

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


meta.description for frigate is: NVR with realtime local object detection for IP cameras

meta.homepage for frigate is: https://github.com/blakeblackshear/frigate

meta.changelog for frigate is: https://github.com/blakeblackshear/frigate/releases/tag/v0.13.2


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

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- Warning: a test defined in `passthru.tests` did not pass
- found 0.13.2 with grep in /nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2
- found 0.13.2 in filename of file in /nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2

---

<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
frigate
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2 \
  --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 frigate https://github.com/r-ryantm/nixpkgs/archive/b0d8a540a96f9ba77cee0e66e394a51baddc6a44.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/b0d8a540a96f9ba77cee0e66e394a51baddc6a44#frigate
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2
ls -la /nix/store/x3q74lsj3zg8r7gwx660d8yyzb783ihm-frigate-0.13.2/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>frigate</li>
  </ul>
</details>

---

###### Maintainer pings

cc @mweinelt 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/289933