python311Packages.numba 0 -> 1
attrpath: python311Packages.numba
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
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] Success
[updateScript] this derivation will be built:
  /nix/store/advy4k470klk0w3yl96nrsqy641mziws-packages.json.drv
building '/nix/store/advy4k470klk0w3yl96nrsqy641mziws-packages.json.drv'...

Going to be running update for following packages:
 - python3.11-numba-0.59.0

Press Enter key to continue...
Running update for:
 - python3.11-numba-0.59.0: UPDATING ...
 - python3.11-numba-0.59.0: DONE.

Packages updated!

Diff after rewrites:
diff --git a/pkgs/development/python-modules/numba/default.nix b/pkgs/development/python-modules/numba/default.nix
index ecc987156fc1..5da54824a3c4 100644
--- a/pkgs/development/python-modules/numba/default.nix
+++ b/pkgs/development/python-modules/numba/default.nix
@@ -32,7 +32,7 @@ let
 in buildPythonPackage rec {
   # Using an untagged version, with numpy 1.25 support, when it's released
   # also drop the versioneer patch in postPatch
-  version = "0.59.0";
+  version = "0.59.1";
   pname = "numba";
   pyproject = true;
 
@@ -54,7 +54,7 @@ in buildPythonPackage rec {
     # use `forceFetchGit = true;`.` If in the future we'll observe the hash
     # changes too often, we can always use forceFetchGit, and inject the
     # relevant strings ourselves, using `sed` commands, in extraPostFetch.
-    hash = "sha256-wd4TujPhV2Jy/HUUXLHAlcbVFm4gfQNWxWFXD+jeZC4=";
+    hash = "sha256-4udpgLLHbHNtxPiYVkj+gxAjTWV3ClZOv98Y313/qbc=";
   };
 
   postPatch = ''

An auto update branch exists with message `python311Packages.numba: 0.59.0 -> 0.59.1`. New version is 0.59.1.
An auto update branch exists with an equal or greater version