Running nixpkgs-update (https://nix-community.org/update-bot/) with UPDATE_INFO: bats 1.12.0 -> 1.14.0 https://github.com/bats-core/bats-core/releases attrpath: bats Checking auto update branch... An auto update branch exists with message `bats: 1.12.0 -> 1.13.0`. New version is 1.14.0. The auto update branch does not match or exceed the new version. [version] [version] updated version and sha256 [rustCrateVersion] [rustCrateVersion] No cargoHash found [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/ba/bats/package.nix b/pkgs/by-name/ba/bats/package.nix index 64b2dea84c7a..b3f58b58499d 100644 --- a/pkgs/by-name/ba/bats/package.nix +++ b/pkgs/by-name/ba/bats/package.nix @@ -29,13 +29,13 @@ resholve.mkDerivation (finalAttrs: { pname = "bats"; - version = "1.12.0"; + version = "1.14.0"; src = fetchFromGitHub { owner = "bats-core"; repo = "bats-core"; rev = "v${finalAttrs.version}"; - hash = "sha256-5VCkOzyaUOBW+HVVHDkH9oCWDI/MJW6yrLTQG60Ralk="; + hash = "sha256-pUuSjXxMCFLlsTvErgerHLnaQmcA9eXuKZKRkuOGJ8k="; }; patchPhase = '' 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: `3aff4d1c49432f147c27526886d6cd5f383ba642` --- ### `x86_64-linux`
:x: 3 packages failed to build:
:white_check_mark: 8 packages 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/bats-core/bats-core/releases. meta.description for bats is: Bash Automated Testing System meta.homepage for bats is: https://github.com/bats-core/bats-core ###### Updates performed - Version update ###### To inspect upstream changes - [Release on GitHub](https://github.com/bats-core/bats-core/releases/tag/v1.14.0) - [Compare changes on GitHub](https://github.com/bats-core/bats-core/compare/v1.12.0...v1.14.0) ###### Impact Checks done --- - built on NixOS - The tests defined in `passthru.tests`, if any, passed - found 1.14.0 with grep in /nix/store/2cjdmynshhm3nrhf7250d8x6gjl1pv51-bats-1.14.0 - found 1.14.0 in filename of file in /nix/store/2cjdmynshhm3nrhf7250d8x6gjl1pv51-bats-1.14.0 ---
Rebuild report (if merged into master) (click to expand) ``` 14 total rebuild path(s) 12 package rebuild(s) First fifty rebuilds by attrpath bash-preexec bats crypt4gh kicadAddons.kikit kicadAddons.kikit-library kikit locate-dominating-file packcc python313Packages.crypt4gh python314Packages.crypt4gh scap-security-guide ```
Instructions to test this update (click to expand) --- Either **download from the cache**: ``` nix-store -r /nix/store/2cjdmynshhm3nrhf7250d8x6gjl1pv51-bats-1.14.0 \ --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 bats https://github.com/r-ryantm/nixpkgs/archive/3aff4d1c49432f147c27526886d6cd5f383ba642.tar.gz ``` Or: ``` nix build github:r-ryantm/nixpkgs/3aff4d1c49432f147c27526886d6cd5f383ba642#bats ``` After you've downloaded or built it, look at the files and if there are any, run the binaries: ``` ls -la /nix/store/2cjdmynshhm3nrhf7250d8x6gjl1pv51-bats-1.14.0 ls -la /nix/store/2cjdmynshhm3nrhf7250d8x6gjl1pv51-bats-1.14.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. ## `nixpkgs-review` result Generated using [`nixpkgs-review`](https://github.com/Mic92/nixpkgs-review). Command: `nixpkgs-review --extra-nixpkgs-config '{ allowBroken = false; }'` Commit: `3aff4d1c49432f147c27526886d6cd5f383ba642` --- ### `x86_64-linux`
:x: 3 packages failed to build:
:white_check_mark: 8 packages built:
--- ###### Maintainer pings cc @abathur 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). Updated existing PR https://api.github.com/repos/NixOS/nixpkgs/pulls/459569