Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: flamelens 0.3.1 -> 0.4.0 https://github.com/YS-L/flamelens/releases
attrpath: flamelens
Checking auto update branch...
No auto update branch exists
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] Replacing cargoHash with sha256-QcEN83Cd92i0Ll+8uWSLREKk5i0STwhAKTCx48BiI6A=
[rustCrateVersion] Finished updating Crate version and replacing hashes
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/by-name/fl/flamelens/package.nix b/pkgs/by-name/fl/flamelens/package.nix
index aea1bd4d963b..a090637037aa 100644
--- a/pkgs/by-name/fl/flamelens/package.nix
+++ b/pkgs/by-name/fl/flamelens/package.nix
@@ -6,16 +6,16 @@
 
 rustPlatform.buildRustPackage (finalAttrs: {
   pname = "flamelens";
-  version = "0.3.1";
+  version = "0.4.0";
 
   src = fetchFromGitHub {
     owner = "YS-L";
     repo = "flamelens";
     tag = "v${finalAttrs.version}";
-    hash = "sha256-cvsBeV9pdgr8V+82Fw/XZS1Ljq/7ff4JYMHnNxqNvOM=";
+    hash = "sha256-b7lRMyeX/aL1ziSaLBUxChrwXeKNhcCShjGY6ANYqhY=";
   };
 
-  cargoHash = "sha256-FIIt8RwPaPrVG3D9FoMjR4L81NzUrKZsAeW2AJkBG1o=";
+  cargoHash = "sha256-QcEN83Cd92i0Ll+8uWSLREKk5i0STwhAKTCx48BiI6A=";
 
   meta = {
     description = "Interactive flamegraph viewer in the terminal";

Successfully finished processing
[check][nixpkgs-review]
[check][nixpkgs-review] report.md does not exist
:x: nixpkgs-review failed
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/YS-L/flamelens/releases.

meta.description for flamelens is: Interactive flamegraph viewer in the terminal

meta.homepage for flamelens is: https://github.com/YS-L/flamelens

meta.changelog for flamelens is: https://github.com/YS-L/flamelens/releases/tag/v0.4.0/CHANGELOG.md


###### Updates performed
- Rust version update

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

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

---

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

```
2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

flamelens
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/rg3c2d2m1dsbiqqd8hwb0nz0c1zn268m-flamelens-0.4.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 flamelens https://github.com/r-ryantm/nixpkgs/archive/5379ceec9407c92009b6ced52e067a463309b637.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/5379ceec9407c92009b6ced52e067a463309b637#flamelens
```

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

:x: nixpkgs-review failed

---

###### Maintainer pings

cc @AaronVerDow 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/493710