Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bpftrace 0.26.0 -> 0.26.1 https://github.com/bpftrace/bpftrace/releases
attrpath: bpftrace
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoHash found
[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/bp/bpftrace/package.nix b/pkgs/by-name/bp/bpftrace/package.nix
index 6aa70674c9b9..431991c2e6ae 100644
--- a/pkgs/by-name/bp/bpftrace/package.nix
+++ b/pkgs/by-name/bp/bpftrace/package.nix
@@ -23,13 +23,13 @@
 
 stdenv.mkDerivation rec {
   pname = "bpftrace";
-  version = "0.26.0";
+  version = "0.26.1";
 
   src = fetchFromGitHub {
     owner = "bpftrace";
     repo = "bpftrace";
     rev = "v${version}";
-    hash = "sha256-NYMMQKOWCLbECQX1FPYaLcQyO3H+LHCw02bF1sWsMuY=";
+    hash = "sha256-h3gFnQq48oM5uK07xrykOCSJxhr6dqcyVUDoIKIRREY=";
   };
 
   buildInputs = with llvmPackages; [

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

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>bpftrace</li>
    <li>fence</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 https://github.com/bpftrace/bpftrace/releases.

meta.description for bpftrace is: High-level tracing language for Linux eBPF

meta.homepage for bpftrace is: https://github.com/bpftrace/bpftrace

meta.changelog for bpftrace is: https://github.com/bpftrace/bpftrace/releases/tag/v0.26.1


###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/bpftrace/bpftrace/releases/tag/v0.26.1)

- [Compare changes on GitHub](https://github.com/bpftrace/bpftrace/compare/v0.26.0...v0.26.1)

###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 0.26.1 in filename of file in /nix/store/mfyjcp8804z8jshc9pj3j8gn6xw033rm-bpftrace-0.26.1

---

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

```
20 total rebuild path(s)

20 package rebuild(s)

First fifty rebuilds by attrpath

bpftrace
fence
linuxKernel.packages.linux_5_10.bpftrace
linuxKernel.packages.linux_5_15.bpftrace
linuxKernel.packages.linux_6_1.bpftrace
linuxKernel.packages.linux_6_12.bpftrace
linuxKernel.packages.linux_6_18.bpftrace
linuxKernel.packages.linux_6_6.bpftrace
linuxKernel.packages.linux_7_0.bpftrace
linuxKernel.packages.linux_xanmod.bpftrace
linuxKernel.packages.linux_xanmod_latest.bpftrace
linuxKernel.packages.linux_xanmod_stable.bpftrace
linuxKernel.packages.linux_zen.bpftrace
linuxPackages.bpftrace
linuxPackages_latest.bpftrace
linuxPackages_xanmod.bpftrace
linuxPackages_xanmod_latest.bpftrace
linuxPackages_xanmod_stable.bpftrace
linuxPackages_zen.bpftrace
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/mfyjcp8804z8jshc9pj3j8gn6xw033rm-bpftrace-0.26.1 \
  --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 bpftrace https://github.com/r-ryantm/nixpkgs/archive/ee347c19bb9d8275c4c006477450ffd6db498ef6.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/ee347c19bb9d8275c4c006477450ffd6db498ef6#bpftrace
```

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

## `nixpkgs-review` result

Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).

Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `ee347c19bb9d8275c4c006477450ffd6db498ef6`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>bpftrace</li>
    <li>fence</li>
  </ul>
</details>

---

###### Maintainer pings

cc @rvl @thoughtpolice @martinetd @mfrw @illustris 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/528191