k3s 0 -> 1
attrpath: k3s
Checking auto update branch...
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] skipping because derivation has updateScript
[updateScript] 
[updateScript] Success
[updateScript] this derivation will be built:
  /nix/store/zy3v1pzp2srnjm5xc5a9wwfgp3rb38m4-packages.json.drv
building '/nix/store/zy3v1pzp2srnjm5xc5a9wwfgp3rb38m4-packages.json.drv'...

Going to be running update for following packages:
 - k3s-1.26.3+k3s1

Press Enter key to continue...
Running update for:
 - k3s-1.26.3+k3s1: UPDATING ...
 - k3s-1.26.3+k3s1: DONE.

Packages updated!


[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/applications/networking/cluster/k3s/1_26/default.nix b/pkgs/applications/networking/cluster/k3s/1_26/default.nix
index 558e800cedf..f7dbe7e6839 100644
--- a/pkgs/applications/networking/cluster/k3s/1_26/default.nix
+++ b/pkgs/applications/networking/cluster/k3s/1_26/default.nix
@@ -47,10 +47,10 @@
 # Those pieces of software we entirely ignore upstream's handling of, and just
 # make sure they're in the path if desired.
 let
-  k3sVersion = "1.26.3+k3s1";     # k3s git tag
-  k3sCommit = "01ea3ff27be0b04f945179171cec5a8e11a14f7b"; # k3s git commit at the above version
-  k3sRepoSha256 = "1wpciikmr4l2nw92i3wlz301vxjiyz8rlzkn8jhzcaiifykc565s";
-  k3sVendorSha256 = "sha256-1HFLj3zSHV7RvA0fsQ/dPzwnkSRqE9TXXDA4m8OhwZE=";
+  k3sVersion = "1.26.4+k3s1";     # k3s git tag
+  k3sCommit = "8d0255af07e95b841952563253d27b0d10bd72f0"; # k3s git commit at the above version
+  k3sRepoSha256 = "0qlszdnlsvj3hzx2p0wl3zhaw908w8a62z6vlf2g69a3c75f55cs";
+  k3sVendorSha256 = "sha256-JXTsZYtTspu/pWMRSS2BcegktawBJ6BK7YEKbz1J/ao=";
 
   # nix generated by update.sh
   # Based on the traefik charts here: https://github.com/k3s-io/k3s/blob/d71ab6317e22dd34673faa307a412a37a16767f6/scripts/download#L29-L32

No auto update branch exists
Successfully finished processing
cachix "/nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>k3s</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from passthru.updateScript.


meta.description for k3s is: A lightweight Kubernetes distribution

meta.homepage for k3s is: https://k3s.io




###### Updates performed
- Ran passthru.UpdateScript

###### To inspect upstream changes





###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 1.26.4+k3s1 with grep in /nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1
- found 1.26.4+k3s1 in filename of file in /nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1

---

</details>
<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
k3s
k3s_1_26
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '
```
(The Cachix cache is only trusted for this store-path realization.)
For the Cachix 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 k3s https://github.com/r-ryantm/nixpkgs/archive/c78b94421357e9afc76dd11a08779b606101674e.tar.gz
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1
ls -la /nix/store/8i95z36mjvgl1f5h72igfnqc75dqv5dh-k3s-1.26.4+k3s1/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.

Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>k3s</li>
  </ul>
</details>

---

###### Maintainer pings

cc @euank @Mic92 @yajo for [testing](https://github.com/ryantm/nixpkgs-update/blob/master/doc/nixpkgs-maintainer-faq.md#r-ryantm-opened-a-pr-for-my-package-what-do-i-do).
https://api.github.com/repos/NixOS/nixpkgs/pulls/227405