commitizen 0 -> 1
attrpath: commitizen
Checking auto update branch...
[version]
[version] skipping because derivation has updateScript
[rustCrateVersion]
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion]
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[updateScript]
[updateScript] Success
[updateScript] this derivation will be built:
/nix/store/w14xgcf06bnyqqrlj7dzpcv0zhj0l211-packages.json.drv
building '/nix/store/w14xgcf06bnyqqrlj7dzpcv0zhj0l211-packages.json.drv'...
Going to be running update for following packages:
- commitizen-2.41.0
Press Enter key to continue...
Running update for:
- commitizen-2.41.0: UPDATING ...
- commitizen-2.41.0: DONE.
Packages updated!
[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/applications/version-management/commitizen/default.nix b/pkgs/applications/version-management/commitizen/default.nix
index f53c6fb153b..04a810cf9e8 100644
--- a/pkgs/applications/version-management/commitizen/default.nix
+++ b/pkgs/applications/version-management/commitizen/default.nix
@@ -26,13 +26,13 @@
buildPythonApplication rec {
pname = "commitizen";
- version = "2.41.0";
+ version = "2.42.0";
src = fetchFromGitHub {
owner = "commitizen-tools";
repo = pname;
rev = "v${version}";
- hash = "sha256-dzAIRfUdyHSefDRDuPMsr8l2Dsiall2ZUDB6GufTbXE=";
+ hash = "sha256-13WEbF6in+zYZXWYqlYA98qJkKxjmcpQY9GuGS+DDtk=";
};
format = "pyproject";
No auto update branch exists
Successfully finished processing
cachix "/nix/store/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.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 passthru.updateScript.
meta.description for commitizen is: Tool to create committing rules for projects, auto bump versions, and generate changelogs
meta.homepage for commitizen is: https://github.com/commitizen-tools/commitizen
meta.changelog for commitizen is: https://github.com/commitizen-tools/commitizen/blob/v2.42.0/CHANGELOG.md
###### Updates performed
- Ran passthru.UpdateScript
###### To inspect upstream changes
- [Compare changes on GitHub](https://github.com/commitizen-tools/commitizen/compare/v2.41.0...v2.42.0)
###### Impact
Checks done (click to expand)
---
- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2.42.0 with grep in /nix/store/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.0
- found 2.42.0 in filename of file in /nix/store/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.0
---
Rebuild report (if merged into master) (click to expand)
```
1 total rebuild path(s)
1 package rebuild(s)
First fifty rebuilds by attrpath
commitizen
```
Instructions to test this update (click to expand)
---
Either **download from Cachix**:
```
nix-store -r /nix/store/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.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 commitizen https://github.com/r-ryantm/nixpkgs/archive/5636940545b6fae90f589d385113866d1140976e.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/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.0
ls -la /nix/store/d2pvsj0cqaskza5rsqnp3l9gwj6rhm2w-commitizen-2.42.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 @lovesegfault @anthonyroussel 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/215927