Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: field-monitor 50.1 -> 51.0 https://github.com/theCapypara/field-monitor/releases
attrpath: field-monitor
Checking auto update branch...
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] No cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] this derivation will be built:
  /nix/store/lk1yxvg814h3h082nkb1210yvd0y671p-packages.json.drv
building '/nix/store/lk1yxvg814h3h082nkb1210yvd0y671p-packages.json.drv'...
structuredAttrs is enabled

Going to be running update for following packages:
 - field-monitor-50.1

Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
 - field-monitor-50.1: UPDATING ...
 - field-monitor-50.1: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/fi/field-monitor/package.nix b/pkgs/by-name/fi/field-monitor/package.nix
index 64dd5c53b7b9..63316cbaff1b 100644
--- a/pkgs/by-name/fi/field-monitor/package.nix
+++ b/pkgs/by-name/fi/field-monitor/package.nix
@@ -34,7 +34,7 @@
 }:
 stdenv.mkDerivation (finalAttrs: {
   pname = "field-monitor";
-  version = "50.1";
+  version = "51.0";
 
   strictDeps = true;
 
@@ -42,12 +42,12 @@ stdenv.mkDerivation (finalAttrs: {
     owner = "theCapypara";
     repo = "field-monitor";
     tag = "v${finalAttrs.version}";
-    hash = "sha256-waMa70oLKvIoljvE+MjWWKVL1Cd0xnasVeB17tfMQW8=";
+    hash = "sha256-A7NDb6kpD1XzP43jbc5DSZ2bKoCWWmtTHFY3okC8PHY=";
   };
 
   cargoDeps = rustPlatform.fetchCargoVendor {
     inherit (finalAttrs) pname version src;
-    hash = "sha256-fsrczFhoIilxgZRH2PVXC67YdkMsIjA6zTfix57TTzo=";
+    hash = "sha256-PLblOFgFJ5CoT9j6OvoQjJZPOVvrveFvWkIFd0LBaiw=";
   };
 
   mesonBuildType = "release";

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: `922f00b54f77183043e83f992a0f92cf88dcc38c`

---
### `x86_64-linux`
<details>
  <summary>✅ 1 package built:</summary>
  <ul>
    <li>field-monitor</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 field-monitor is: Viewer for virtual machines and other external screens

meta.homepage for field-monitor is: https://github.com/theCapypara/field-monitor




###### 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 51.0 with grep in /nix/store/gkphhr6igwc2mnkhk97zh0f4cgwchkvp-field-monitor-51.0
- found 51.0 in filename of file in /nix/store/gkphhr6igwc2mnkhk97zh0f4cgwchkvp-field-monitor-51.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

field-monitor
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/gkphhr6igwc2mnkhk97zh0f4cgwchkvp-field-monitor-51.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 field-monitor https://github.com/r-ryantm/nixpkgs/archive/922f00b54f77183043e83f992a0f92cf88dcc38c.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/922f00b54f77183043e83f992a0f92cf88dcc38c#field-monitor
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/gkphhr6igwc2mnkhk97zh0f4cgwchkvp-field-monitor-51.0
ls -la /nix/store/gkphhr6igwc2mnkhk97zh0f4cgwchkvp-field-monitor-51.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: `922f00b54f77183043e83f992a0f92cf88dcc38c`

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

---

###### Maintainer pings

cc @theCapypara 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/565826