Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: fvm 4.1.2 -> 4.3.0 https://github.com/conceptadev/fvm/releases
attrpath: fvm
Checking auto update branch...
[version] 
[version] skipping because derivation has updateScript
[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/n8v9v9aqidgmxd2n8dsbp5x9pqx7lg5k-packages.json.drv
building '/nix/store/n8v9v9aqidgmxd2n8dsbp5x9pqx7lg5k-packages.json.drv'...

Going to be running update for following packages:
 - fvm-4.1.2

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

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/fv/fvm/package.nix b/pkgs/by-name/fv/fvm/package.nix
index 4b0389aada6b..d9c30c80eff5 100644
--- a/pkgs/by-name/fv/fvm/package.nix
+++ b/pkgs/by-name/fv/fvm/package.nix
@@ -9,13 +9,13 @@
 }:
 
 let
-  version = "4.1.2";
+  version = "4.3.0";
 
   src = fetchFromGitHub {
     owner = "conceptadev";
     repo = "fvm";
     tag = version;
-    hash = "sha256-Kyxyt2UsrQ6Bc6EuYJjpEFdYwcus2/bcVrWsd/gs3Ok=";
+    hash = "sha256-SAWWKNbE/TyrP5bcIdDeAZa6/3d4D/Ru1PbcPvy9EDo=";
   };
 in
 buildDartApplication {

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: `baa04ff3bd13d40112969ae999d94a98253a346c`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>fvm</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 fvm is: Simple CLI to manage Flutter SDK versions

meta.homepage for fvm is: https://github.com/conceptadev/fvm




###### 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 4.3.0 with grep in /nix/store/qnz59b1rng99ms3qjn0dzaf4dd6s6q86-fvm-4.3.0
- found 4.3.0 in filename of file in /nix/store/qnz59b1rng99ms3qjn0dzaf4dd6s6q86-fvm-4.3.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

fvm
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/qnz59b1rng99ms3qjn0dzaf4dd6s6q86-fvm-4.3.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 fvm https://github.com/r-ryantm/nixpkgs/archive/baa04ff3bd13d40112969ae999d94a98253a346c.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/baa04ff3bd13d40112969ae999d94a98253a346c#fvm
```

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

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

---

###### Maintainer pings



> [!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/556660