eks-node-viewer 0.2.1 -> 0.4.0 https://github.com/awslabs/eks-node-viewer/releases attrpath: eks-node-viewer Checking auto update branch... No auto update branch exists [version] [version] generic version rewriter does not support multiple hashes [rustCrateVersion] [rustCrateVersion] No cargoSha256 or cargoHash found [golangModuleVersion] [golangModuleVersion] Found old vendorHash = "sha256-28TKZYZM2kddXAusxmjhrKFy+ATU7kZM4Ad7zvP/F3A=" [golangModuleVersion] Replaced vendorHash with sha256-L1lG+b7MiJQvLqZuLdSjh5zAaApvWdi9SZSDPvObW5w= [golangModuleVersion] Finished updating vendorHash [updateScript] [updateScript] skipping because derivation has no updateScript [quotedUrls] [quotedUrls] nothing found to replace Diff after rewrites: diff --git a/pkgs/applications/networking/cluster/eks-node-viewer/default.nix b/pkgs/applications/networking/cluster/eks-node-viewer/default.nix index 10db2817962..044d2d25516 100644 --- a/pkgs/applications/networking/cluster/eks-node-viewer/default.nix +++ b/pkgs/applications/networking/cluster/eks-node-viewer/default.nix @@ -2,16 +2,16 @@ buildGoModule rec { pname = "eks-node-viewer"; - version = "0.2.1"; + version = "0.4.0"; src = fetchFromGitHub { owner = "awslabs"; repo = pname; rev = "v${version}"; - sha256 = "sha256-XRt9a//0mYKZKsMs2dlcsBt5ikC9ZBMeQ3Vas0eT8a8="; + sha256 = "sha256-p0n7ocoMBgM6i7e6yX+NDIkZBcJ3dT6VNWPihCheeC0="; }; - vendorHash = "sha256-28TKZYZM2kddXAusxmjhrKFy+ATU7kZM4Ad7zvP/F3A="; + vendorHash = "sha256-L1lG+b7MiJQvLqZuLdSjh5zAaApvWdi9SZSDPvObW5w="; meta = with lib; { description = "Tool to visualize dynamic node usage within a cluster"; Successfully finished processing cachix "/nix/store/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0" [check][nixpkgs-review] Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
1 package 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/awslabs/eks-node-viewer/releases. meta.description for eks-node-viewer is: Tool to visualize dynamic node usage within a cluster meta.homepage for eks-node-viewer is: https://github.com/awslabs/eks-node-viewer meta.changelog for eks-node-viewer is: https://github.com/awslabs/eks-node-viewer/releases/tag/0.4.0 ###### Updates performed - Golang update ###### To inspect upstream changes - [Release on GitHub](https://github.com/awslabs/eks-node-viewer/releases/tag/v0.4.0) - [Compare changes on GitHub](https://github.com/awslabs/eks-node-viewer/compare/v0.2.1...v0.4.0) ###### Impact
Checks done (click to expand) --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 0.4.0 with grep in /nix/store/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0 - found 0.4.0 in filename of file in /nix/store/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0 ---
Rebuild report (if merged into master) (click to expand) ``` 1 total rebuild path(s) 1 package rebuild(s) First fifty rebuilds by attrpath eks-node-viewer ```
Instructions to test this update (click to expand) --- Either **download from Cachix**: ``` nix-store -r /nix/store/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0 \ --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 eks-node-viewer https://github.com/r-ryantm/nixpkgs/archive/565efb4ad0b5c8c2ba1c212f75ae880787b7db82.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/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0 ls -la /nix/store/bkmrn6w8ljlyn71ypqg9xj94q80q8ijh-eks-node-viewer-0.4.0/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)
1 package built:
--- ###### Maintainer pings cc @ivankovnatsky 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/237256