Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: cpuid 20250513 -> 20260220 https://repology.org/project/cpuid-etallen/versions
attrpath: cpuid
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/cp/cpuid/package.nix b/pkgs/by-name/cp/cpuid/package.nix
index e0043267b2b2..9156bdd4d577 100644
--- a/pkgs/by-name/cp/cpuid/package.nix
+++ b/pkgs/by-name/cp/cpuid/package.nix
@@ -7,11 +7,11 @@
 
 stdenv.mkDerivation (finalAttrs: {
   pname = "cpuid";
-  version = "20250513";
+  version = "20260220";
 
   src = fetchurl {
     url = "http://etallen.com/cpuid/cpuid-${finalAttrs.version}.src.tar.gz";
-    sha256 = "sha256-b0dKIrWEhIjkVLAaMduA65WNVWdLUzlTP8DmrreTYms=";
+    sha256 = "sha256-52IP11rlkRcfEQxJuZo5EokzoMqtAjto1KOEub4Lj/s=";
   };
 
   # For pod2man during the build process.

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

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>cpuid</li>
    <li>hw-probe</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://repology.org/project/cpuid-etallen/versions.

meta.description for cpuid is: Linux tool to dump x86 CPUID information about the CPU

meta.homepage for cpuid is: http://etallen.com/cpuid.html




###### Updates performed
- Version update

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

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

---

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

```
3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath

cpuid
hw-probe
```

</details>

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

---

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/m85dgpnsg5apsnpwwnfspgmi4q1arrrb-cpuid-20260220
ls -la /nix/store/m85dgpnsg5apsnpwwnfspgmi4q1arrrb-cpuid-20260220/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: `d612562569a1afa11d4e00f1da85f30ce5cf818e`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 2 packages built:</summary>
  <ul>
    <li>cpuid</li>
    <li>hw-probe</li>
  </ul>
</details>

---

###### Maintainer pings

cc @blitz 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/493180