Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: cargo-update 20.0.0 -> 20.0.1 https://github.com/nabijaczleweli/cargo-update/releases
attrpath: cargo-update
Checking auto update branch...
No auto update branch exists
[version]
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion]
[rustCrateVersion] Replacing cargoHash with sha256-LsqDwGboCPGrRmpFqy13anszrwE8+VoqRqfm5K3VgM8=
[rustCrateVersion] Finished updating Crate version and replacing hashes
[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/ca/cargo-update/package.nix b/pkgs/by-name/ca/cargo-update/package.nix
index 2ace34600749..c06c8718e1bc 100644
--- a/pkgs/by-name/ca/cargo-update/package.nix
+++ b/pkgs/by-name/ca/cargo-update/package.nix
@@ -16,14 +16,14 @@
rustPlatform.buildRustPackage (finalAttrs: {
pname = "cargo-update";
- version = "20.0.0";
+ version = "20.0.1";
src = fetchCrate {
inherit (finalAttrs) pname version;
- hash = "sha256-J/FujtsQF8WfHFoHJ3r2M+vv8WVh4cxDFw07JntnW2g=";
+ hash = "sha256-wV1R95TBPLXzCmE9sjztxJdvwvWxedEQPI5TxZEGUqA=";
};
- cargoHash = "sha256-bH8Mg7QQbbXlF7fxwWEFYmYQD1CmDM+g4GhFPZwLy/M=";
+ cargoHash = "sha256-LsqDwGboCPGrRmpFqy13anszrwE8+VoqRqfm5K3VgM8=";
nativeBuildInputs = [
cmake
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: `a0c083b56f90f5d5555d7fa0eaf0ec86262af8f0`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
Automatic update generated by [nixpkgs-update](https://github.com/nix-community/nixpkgs-update) tools. This update was made based on information from https://github.com/nabijaczleweli/cargo-update/releases.
meta.description for cargo-update is: Cargo subcommand for checking and applying updates to installed executables
meta.homepage for cargo-update is: https://github.com/nabijaczleweli/cargo-update
meta.changelog for cargo-update is: https://github.com/nabijaczleweli/cargo-update/releases/tag/v20.0.1
###### Updates performed
- Rust version update
###### To inspect upstream changes
###### Impact
Checks done
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 20.0.1 with grep in /nix/store/rlw1141320m3q6h1865wf4jb4bsljhqp-cargo-update-20.0.1
- found 20.0.1 in filename of file in /nix/store/rlw1141320m3q6h1865wf4jb4bsljhqp-cargo-update-20.0.1
---
Rebuild report (if merged into master) (click to expand)
```
2 total rebuild path(s)
2 package rebuild(s)
First fifty rebuilds by attrpath
cargo-update
```
Instructions to test this update (click to expand)
---
Either **download from the cache**:
```
nix-store -r /nix/store/rlw1141320m3q6h1865wf4jb4bsljhqp-cargo-update-20.0.1 \
--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 cargo-update https://github.com/r-ryantm/nixpkgs/archive/a0c083b56f90f5d5555d7fa0eaf0ec86262af8f0.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/a0c083b56f90f5d5555d7fa0eaf0ec86262af8f0#cargo-update
```
After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/rlw1141320m3q6h1865wf4jb4bsljhqp-cargo-update-20.0.1
ls -la /nix/store/rlw1141320m3q6h1865wf4jb4bsljhqp-cargo-update-20.0.1/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.
## `nixpkgs-review` result
Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review).
Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'`
Commit: `a0c083b56f90f5d5555d7fa0eaf0ec86262af8f0`
---
### `x86_64-linux`
:white_check_mark: 1 package built:
---
###### Maintainer pings
cc @Gerschtli @JohnTitor @matthiasbeyer 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/530097