Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: cef-binary 0 -> 1
attrpath: cef-binary
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/qi5d4d3b0iaqr94h8hid7wsk39rf1r6k-packages.json.drv
building '/nix/store/qi5d4d3b0iaqr94h8hid7wsk39rf1r6k-packages.json.drv'...

Going to be running update for following packages:
 - cef-binary-149.0.5

Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
 - cef-binary-149.0.5: UPDATING ...
 - cef-binary-149.0.5: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/ce/cef-binary/package.nix b/pkgs/by-name/ce/cef-binary/package.nix
index 1e6c30859bf6..2d2ef6d5b7bd 100644
--- a/pkgs/by-name/ce/cef-binary/package.nix
+++ b/pkgs/by-name/ce/cef-binary/package.nix
@@ -29,13 +29,13 @@
   libx11,
   libxshmfence,
   libxcb,
-  version ? "149.0.5",
-  gitRevision ? "6770623",
-  chromiumVersion ? "149.0.7827.197",
+  version ? "151.3.16",
+  gitRevision ? "be1e15d",
+  chromiumVersion ? "151.0.7922.109",
   buildType ? "Release",
   srcHashes ? {
-    aarch64-linux = "sha256-cBAvcvs1rAg5EKJkCt81RZYupCWpUNIC/nLt3PJow7Q=";
-    x86_64-linux = "sha256-OPGMBJmvvLiLdBDniBQwx7LmTGGI59AcesJdILSeqcs=";
+    aarch64-linux = "sha256-gRYcEylZAUvKTOmV1zw9TyiEkv6FZ0vhVT1mLwne57k=";
+    x86_64-linux = "sha256-6usxPmA53kZIVYk9KHxNXrTscSaXjqg8YWS/SiPcAXo=";
   },
 }:
 

An auto update branch exists with message `cef-binary: 149.0.5 -> 150.0.14`. New version is 151.3.16.
The auto update branch does not match or exceed the new version.
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: `8559b58434eb136d1892aa68ea6d680dcb4f3cff`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>graphite</li>
    <li>cef-binary</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 cef-binary is: Simple framework for embedding Chromium-based browsers in other applications

meta.homepage for cef-binary is: https://cef-builds.spotifycdn.com/index.html




###### 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 151.3.16 with grep in /nix/store/gz1q7am8jkmqrshhx9hxicrm998ylazc-cef-binary-151.3.16
- found 151.3.16 in filename of file in /nix/store/gz1q7am8jkmqrshhx9hxicrm998ylazc-cef-binary-151.3.16

---

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

```
9 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

cef-binary
graphite
```

</details>

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

---

Either **download from the cache**:
```
nix-store -r /nix/store/gz1q7am8jkmqrshhx9hxicrm998ylazc-cef-binary-151.3.16 \
  --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 cef-binary https://github.com/r-ryantm/nixpkgs/archive/8559b58434eb136d1892aa68ea6d680dcb4f3cff.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/8559b58434eb136d1892aa68ea6d680dcb4f3cff#cef-binary
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/gz1q7am8jkmqrshhx9hxicrm998ylazc-cef-binary-151.3.16
ls -la /nix/store/gz1q7am8jkmqrshhx9hxicrm998ylazc-cef-binary-151.3.16/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: `8559b58434eb136d1892aa68ea6d680dcb4f3cff`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>graphite</li>
    <li>cef-binary</li>
  </ul>
</details>

---

###### Maintainer pings

cc @puffnfresh 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).
Updated existing PR
https://api.github.com/repos/NixOS/nixpkgs/pulls/541867