Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: cockpit 0 -> 1
attrpath: cockpit
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] 
Going to be running update for following packages:
 - cockpit-364

Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
 - cockpit-364: UPDATING ...
 - cockpit-364: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/co/cockpit/package.nix b/pkgs/by-name/co/cockpit/package.nix
index 15e75b87da26..2dc918b5b885 100644
--- a/pkgs/by-name/co/cockpit/package.nix
+++ b/pkgs/by-name/co/cockpit/package.nix
@@ -53,13 +53,13 @@ in
 
 stdenv.mkDerivation (finalAttrs: {
   pname = "cockpit";
-  version = "364";
+  version = "365";
 
   src = fetchFromGitHub {
     owner = "cockpit-project";
     repo = "cockpit";
     tag = finalAttrs.version;
-    hash = "sha256-TAX0N6ZQWGr17GpyJS23Q5ES3USU2hxSiI867n6G17I=";
+    hash = "sha256-xOIv+NAO3xs74YQpnyQlU6HyptQ4ZmCt4M92195zI6M=";
     fetchSubmodules = true;
   };
 

No auto update branch exists
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: `ca41f7190b45aa6a21ae01ec7ed74ac68a12d9b3`

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 4 packages built:</summary>
  <ul>
    <li>cockpit-files</li>
    <li>cockpit-machines</li>
    <li>cockpit-podman</li>
    <li>cockpit</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 cockpit is: Web-based graphical interface for servers

meta.homepage for cockpit is: https://cockpit-project.org/

meta.changelog for cockpit is: https://cockpit-project.org/blog/cockpit-365.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 365 with grep in /nix/store/xp08jmk27a35i9vqpqbilj8d49v58j2c-cockpit-365
- found 365 in filename of file in /nix/store/xp08jmk27a35i9vqpqbilj8d49v58j2c-cockpit-365

---

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

```
7 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

cockpit
cockpit-files
cockpit-machines
cockpit-podman
```

</details>

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

---

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

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

---
### `x86_64-linux`
<details>
  <summary>:white_check_mark: 4 packages built:</summary>
  <ul>
    <li>cockpit-files</li>
    <li>cockpit-machines</li>
    <li>cockpit-podman</li>
    <li>cockpit</li>
  </ul>
</details>

---

###### Maintainer pings

cc @alexandru0-dev @andre4ik3 @lucasew 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/547448