kubernetes 1.28.4 -> 1.29.2 https://github.com/kubernetes/kubernetes/releases attrpath: kubernetes Checking auto update branch... An auto update branch exists with message `kubernetes: 1.28.4 -> 1.29.1`. New version is 1.29.2. The auto update branch does not match or exceed the new version. [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Found old vendorHash = null [golangModuleVersion] Set vendorHash to null [golangModuleVersion] Finished updating vendorHash [npmDepsVersion] [npmDepsVersion] No npmDepsHash [updateScript] [updateScript] skipping because derivation has no updateScript Diff after rewrites: diff --git a/pkgs/applications/networking/cluster/kubernetes/default.nix b/pkgs/applications/networking/cluster/kubernetes/default.nix index f67d650e77a5..5e8cfc2b166c 100644 --- a/pkgs/applications/networking/cluster/kubernetes/default.nix +++ b/pkgs/applications/networking/cluster/kubernetes/default.nix @@ -20,13 +20,13 @@ buildGoModule rec { pname = "kubernetes"; - version = "1.28.4"; + version = "1.29.2"; src = fetchFromGitHub { owner = "kubernetes"; repo = "kubernetes"; rev = "v${version}"; - hash = "sha256-aaGcAIyy0hFJGFfOq5FaF0qAlygXcs2WcwgvMe5dkbo="; + hash = "sha256-DFQaDlp8CqN0jKTVO5N9ZQYyM2gm/VnQfO4/bfvYrTE="; }; vendorHash = null; Successfully finished processing cachix "/nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2" [check][nixpkgs-review] Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
8 packages built:
Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases. meta.description for kubernetes is: Production-Grade Container Scheduling and Management meta.homepage for kubernetes is: https://kubernetes.io ###### Updates performed - Golang update ###### To inspect upstream changes - [Release on GitHub](https://github.com/kubernetes/kubernetes/releases/tag/v1.29.2) - [Compare changes on GitHub](https://github.com/kubernetes/kubernetes/compare/v1.28.4...v1.29.2) ###### Impact Checks done --- - built on NixOS - Warning: a test defined in `passthru.tests` did not pass - found 1.29.2 with grep in /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2 - found 1.29.2 in filename of file in /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2 ---
Rebuild report (if merged into master) (click to expand) ``` 8 total rebuild path(s) 8 package rebuild(s) First fifty rebuilds by attrpath chart-testing gsctl kns kubectl kubectl-convert kubernetes kubetail tubekit ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2 \ --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 kubernetes https://github.com/r-ryantm/nixpkgs/archive/dffc7922ae07841bb8cff0fced1ceb30b3e12384.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/dffc7922ae07841bb8cff0fced1ceb30b3e12384#kubernetes ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2 ls -la /nix/store/1ymn3pqxc59sqf81z60y18mnd0r1ihwn-kubernetes-1.29.2/bin ``` ---

### 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)
8 packages built:
--- ###### Maintainer pings cc @johanot @offlinehacker @saschagrunert @srhb 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). Updated existing PR https://api.github.com/repos/NixOS/nixpkgs/pulls/274635