Running nixpkgs-update (https://github.com/NixOS/infra/blob/main/non-critical-infra/modules/nixpkgs-update/README.md) with UPDATE_INFO: datadog-pup 2.3.3 -> 2.4.2 https://github.com/DataDog/pup/releases
attrpath: datadog-pup
Checking auto update branch...
[version] 
[version] generic version rewriter does not support multiple hashes
[rustCrateVersion] 
[rustCrateVersion] skipping because derivation has updateScript
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] this derivation will be built:
  /nix/store/258mva8f1n1wi50anxzii8r98imisnyg-packages.json.drv
building '/nix/store/258mva8f1n1wi50anxzii8r98imisnyg-packages.json.drv'...

Going to be running update for following packages:
 - datadog-pup-2.3.3

Press Enter key to continue...
Running update for:
Enqueuing group of 1 packages
 - datadog-pup-2.3.3: UPDATING ...
 - datadog-pup-2.3.3: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/by-name/da/datadog-pup/package.nix b/pkgs/by-name/da/datadog-pup/package.nix
index 1292342b106a..b8d99b9ad3d1 100644
--- a/pkgs/by-name/da/datadog-pup/package.nix
+++ b/pkgs/by-name/da/datadog-pup/package.nix
@@ -11,7 +11,7 @@
 
 rustPlatform.buildRustPackage (finalAttrs: {
   pname = "datadog-pup";
-  version = "2.3.3";
+  version = "2.4.2";
 
   __structuredAttrs = true;
 
@@ -19,10 +19,10 @@ rustPlatform.buildRustPackage (finalAttrs: {
     owner = "DataDog";
     repo = "pup";
     tag = "v${finalAttrs.version}";
-    hash = "sha256-pk/ak21mY+k0TNoH7SaVVWysdGmhwfSvaNFJFoGSbFU=";
+    hash = "sha256-wDTGX6jmOidYKB1cN2srUKERdkIBLYT8Dc4JMkLzFUA=";
   };
 
-  cargoHash = "sha256-8OEL9r+yKBjfEeaenQ1B14NvLJeq5alnmZIoD1v5e4Y=";
+  cargoHash = "sha256-VLq2yAWomIdLj6AxMheN1gLPZxoZXTsdWnBhrnT5YIk=";
 
   checkType = "debug";
   dontUseCargoParallelTests = true;

No auto update branch exists
Received ExitFailure 1 when running
Raw command: nix-build --option sandbox true --arg config "{ allowUnfree = true; allowAliases = false; }" --arg overlays "[ ]" -A datadog-pup
nix build failed.
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_PATH
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_LIBDIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64-unknown-linux-gnu
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR_x86_64_unknown_linux_gnu
  cargo:rerun-if-env-changed=HOST_PKG_CONFIG_SYSROOT_DIR
  cargo:rerun-if-env-changed=PKG_CONFIG_SYSROOT_DIR

  --- stderr

  thread 'main' (1246) panicked at /build/datadog-pup-2.4.2-vendor/source-registry-0/zstd-sys-2.0.16+zstd.1.5.7/build.rs:60:10:
  Can't probe for zstd in pkg-config: Could not run `PKG_CONFIG_ALLOW_SYSTEM_LIBS=1 PKG_CONFIG_ALLOW_SYSTEM_CFLAGS=1 pkg-config --static --libs --cflags libzstd`
  The pkg-config command could not be found.

  Most likely, you need to install a pkg-config package for your OS.
  Try `apt install pkg-config`, or `yum install pkg-config`, or `brew install pkgconf`
  or `pkg install pkg-config`, or `apk add pkgconfig` depending on your distribution.

  If you've already installed it, ensure the pkg-config command is one of the
  directories in the PATH environment variable.

  If you did not expect this build to link to a pre-installed system library,
  then check documentation of the zstd-sys crate for an option to
  build the library from source, or disable features or dependencies
  that require pkg-config.
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...