bandit 1.7.6 -> 1.7.7 https://repology.org/project/bandit/versions
attrpath: bandit
Checking auto update branch...
No auto update branch exists
[version] 
[version] updated version and sha256
[rustCrateVersion] 
[rustCrateVersion] No cargoSha256 or cargoHash found
[golangModuleVersion] 
[golangModuleVersion] Not a buildGoModule package with vendorSha256 or vendorHash
[npmDepsVersion] 
[npmDepsVersion] No npmDepsHash
[updateScript] 
[updateScript] skipping because derivation has no updateScript
Diff after rewrites:
diff --git a/pkgs/development/python-modules/bandit/default.nix b/pkgs/development/python-modules/bandit/default.nix
index 7d7464ec74da..f2f30079954d 100644
--- a/pkgs/development/python-modules/bandit/default.nix
+++ b/pkgs/development/python-modules/bandit/default.nix
@@ -12,14 +12,14 @@
 
 buildPythonPackage rec {
   pname = "bandit";
-  version = "1.7.6";
+  version = "1.7.7";
   format = "setuptools";
 
   disabled = pythonOlder "3.8";
 
   src = fetchPypi {
     inherit pname version;
-    hash = "sha256-cs57yXQTdNlvsvHJqJYIKYhfEkP/3nQ95woZzuNT6PM=";
+    hash = "sha256-UnkGvsYIjLSZquMbyWKGS053Vp6dUp7lHfOpO0uKsoo=";
   };
 
   nativeBuildInputs = [

Successfully finished processing
cachix "/nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>1 package failed to build:</summary>
  <ul>
    <li>prospector</li>
  </ul>
</details>
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>bandit (python311Packages.bandit)</li>
  </ul>
</details>

Automatic update generated by [nixpkgs-update](https://github.com/ryantm/nixpkgs-update) tools. This update was made based on information from https://repology.org/project/bandit/versions.


meta.description for bandit is: Security oriented static analyser for python code

meta.homepage for bandit is: https://bandit.readthedocs.io/

meta.changelog for bandit is: https://github.com/PyCQA/bandit/releases/tag/1.7.7


###### Updates performed
- Version update

###### To inspect upstream changes





###### Impact

<b>Checks done</b>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 1.7.7 with grep in /nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7
- found 1.7.7 in filename of file in /nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7

---

<details>
<summary>
<b>Rebuild report</b> (if merged into master) (click to expand)
</summary>

```
3 total rebuild path(s)

3 package rebuild(s)

First fifty rebuilds by attrpath
bandit
prospector
python311Packages.bandit
```

</details>

<details>
<summary>
<b>Instructions to test this update</b> (click to expand)
</summary>

---

Either **download from Cachix**:
```
nix-store -r /nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7 \
  --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 bandit https://github.com/r-ryantm/nixpkgs/archive/72b7ca4e9511fa5ae16f002a466df43177ae0cad.tar.gz
```
Or:
```
nix build github:r-ryantm/nixpkgs/72b7ca4e9511fa5ae16f002a466df43177ae0cad#bandit
```

After you've downloaded or built it, look at the files and if there are any, run the binaries:
```
ls -la /nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7
ls -la /nix/store/fw76k40sfn870xkkl2nn774vla0zn0hg-python3.11-bandit-1.7.7/bin
```

---

</details>
<br/>



### 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)
<details>
  <summary>1 package failed to build:</summary>
  <ul>
    <li>prospector</li>
  </ul>
</details>
<details>
  <summary>1 package built:</summary>
  <ul>
    <li>bandit (python311Packages.bandit)</li>
  </ul>
</details>

---

###### Maintainer pings

cc @kamadorueda 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/283436