python310Packages.pex 0 -> 1
attrpath: python310Packages.pex
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/6kphmr5ki42nb5zc7xb8bclcq5vns2hb-packages.json.drv
building '/nix/store/6kphmr5ki42nb5zc7xb8bclcq5vns2hb-packages.json.drv'...

Going to be running update for following packages:
 - python3.10-pex-2.1.119

Press Enter key to continue...
Running update for:
 - python3.10-pex-2.1.119: UPDATING ...
 - python3.10-pex-2.1.119: DONE.

Packages updated!


[quotedUrls]
[quotedUrls] nothing found to replace
Diff after rewrites:
diff --git a/pkgs/development/python-modules/pex/default.nix b/pkgs/development/python-modules/pex/default.nix
index 314d3fdfb0e..a8a68d802c8 100644
--- a/pkgs/development/python-modules/pex/default.nix
+++ b/pkgs/development/python-modules/pex/default.nix
@@ -7,14 +7,14 @@
 
 buildPythonPackage rec {
   pname = "pex";
-  version = "2.1.119";
+  version = "2.1.121";
   format = "flit";
 
   disabled = pythonOlder "3.7";
 
   src = fetchPypi {
     inherit pname version;
-    hash = "sha256-QughY8G0Z9/371tlG0VMUqeKW/Nndv9mMbR1AIBlmTA=";
+    hash = "sha256-1mwJnUi/KwDQa+AVGMg034iMGVw+F6UkzxL4Mib6JIk=";
   };
 
   nativeBuildInputs = [

An auto update branch exists with message `python310Packages.pex: 2.1.117 -> 2.1.119`. New version is 2.1.121.
The auto update branch does not match or exceed the new version.
Successfully finished processing
cachix "/nix/store/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121"
[check][nixpkgs-review]
Result of `nixpkgs-review` run on x86_64-linux [1](https://github.com/Mic92/nixpkgs-review)
<details>
  <summary>2 packages built:</summary>
  <ul>
    <li>python310Packages.pex</li>
    <li>python311Packages.pex</li>
  </ul>
</details>

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 python310Packages.pex is: Python library and tool for generating .pex (Python EXecutable) files

meta.homepage for python310Packages.pex is: https://github.com/pantsbuild/pex

meta.changelog for python310Packages.pex is: https://github.com/pantsbuild/pex/releases/tag/v2.1.121


###### Updates performed
- Ran passthru.UpdateScript

###### To inspect upstream changes





###### Impact

<details>
<summary>
<b>Checks done</b> (click to expand)
</summary>

---

- built on NixOS
- The tests defined in `passthru.tests`, if any, passed
- found 2.1.121 with grep in /nix/store/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121
- found 2.1.121 in filename of file in /nix/store/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121

---

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

```
2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.pex
python311Packages.pex
```

</details>

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

---

Either **download from Cachix**:
```
nix-store -r /nix/store/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121 \
  --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 python310Packages.pex https://github.com/r-ryantm/nixpkgs/archive/60439ba8029a73916bdacafe974afbddd76808f4.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/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121
ls -la /nix/store/x38xzid6j275k26f7i5nh0khlsc6qg1n-python3.10-pex-2.1.121/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>2 packages built:</summary>
  <ul>
    <li>python310Packages.pex</li>
    <li>python311Packages.pex</li>
  </ul>
</details>

---

###### Maintainer pings

cc @copumpkin 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).
Updated existing PR
https://api.github.com/repos/NixOS/nixpkgs/pulls/206043