Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: enzyme 0.0.267 -> 0.0.271 https://github.com/EnzymeAD/Enzyme/releases
attrpath: enzyme
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/en/enzyme/package.nix b/pkgs/by-name/en/enzyme/package.nix
index d398f361793c..60df13ea76ef 100644
--- a/pkgs/by-name/en/enzyme/package.nix
+++ b/pkgs/by-name/en/enzyme/package.nix
@@ -7,13 +7,13 @@
 }:
 llvmPackages.stdenv.mkDerivation rec {
   pname = "enzyme";
-  version = "0.0.267";
+  version = "0.0.271";
 
   src = fetchFromGitHub {
     owner = "EnzymeAD";
     repo = "Enzyme";
     rev = "v${version}";
-    hash = "sha256-FoL4m7dxGS05f4fksOYmVyFoS9tlFTc6/v+lB497hog=";
+    hash = "sha256-R3hdy6VSTHBe2ei4aysJhrc++ptQioVe88p/c2CuUP4=";
   };
 
   postPatch = ''

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: `52a5eb34e443944f4d4099364b8086058293f0ed`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 1 package built:</summary>
  <ul>
    <li>enzyme</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/EnzymeAD/Enzyme/releases.

meta.description for enzyme is: High-performance automatic differentiation of LLVM and MLIR

meta.homepage for enzyme is: https://enzyme.mit.edu/




###### Updates performed
- Version update

###### To inspect upstream changes

- [Release on GitHub](https://github.com/EnzymeAD/Enzyme/releases/tag/v0.0.271)

- [Compare changes on GitHub](https://github.com/EnzymeAD/Enzyme/compare/v0.0.267...v0.0.271)

###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 0.0.271 in filename of file in /nix/store/mcbqyasidsc65pz7lgmrd28sam4faxpm-enzyme-0.0.271

---

<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

enzyme
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/mcbqyasidsc65pz7lgmrd28sam4faxpm-enzyme-0.0.271 \
  --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 enzyme https://github.com/r-ryantm/nixpkgs/archive/52a5eb34e443944f4d4099364b8086058293f0ed.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/52a5eb34e443944f4d4099364b8086058293f0ed#enzyme
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/mcbqyasidsc65pz7lgmrd28sam4faxpm-enzyme-0.0.271
ls -la /nix/store/mcbqyasidsc65pz7lgmrd28sam4faxpm-enzyme-0.0.271/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: `52a5eb34e443944f4d4099364b8086058293f0ed`

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

---

###### Maintainer pings

cc @kiranshila 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/534324