python-check-updates
Check and upgrade Python dependency versions against PyPI.
Installation
uv tool install python-check-updates
To upgrade an existing install to the latest version:
uv tool upgrade python-check-updates
Run pcu -v to check the installed version.
Usage
pcu # check all dependencies for updates
pcu -u # upgrade pinned versions and sync
It checks uv toml and fallback to requirements:
pyproject.toml— dependencies, optional-dependencies, dependency-groupsrequirements.txt— dependencies
Filtering upgrades
Combine these flags with -u to restrict which bumps are applied:
--major— include major version bumps--minor— include minor version bumps--patch— include patch version bumps--pin— include pin-only bumps (installed is already at latest, pin string is stale)--drop pkg1 pkg2 ...— exclude named packages from the upgrade set
Flags combine as a union:
pcu -u --minor --patch # minor + patch only, skip major
pcu -u --drop anthropic pydantic # everything except these two
pcu -u --minor --drop cohere # minor bumps, minus cohere
Safe upgrades
Before touching pyproject.toml, uv.lock, or requirements.txt, pcu snapshots the current contents into .pcu/ (which is auto-added to .gitignore). If uv sync or pip install fails, the snapshot is restored and a hint is printed suggesting --drop to exclude suspect packages on retry. On success, .pcu/ is cleaned up.
Output
Package Pinned Installed Latest Status
─────────────────────────────────────────────────────
[dependencies]
httpx >=0.28.1 0.28.1 0.28.3 minor update
pydantic >=2.12.5 2.12.5 2.12.5 up to date
1 package(s) can be updated.
Run pcu -u to upgrade.
Upgrade rewrites version pins in-place, syncs with uv sync or pip install, and verifies.
License
MIT
Metadata
Release files for python-check-updates 0.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| python_check_updates-0.2.2.tar.gz | 30.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| python_check_updates-0.2.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 40.6 kB
Release files / python_check_updates-0.2.2.tar.gz
| Download URL | python_check_updates-0.2.2.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e20bf3ae7c268246b9612daf1a404ec44a1b6f72769baabf957a7e1014ba421
|
|
BLAKE2b-256 checksum How to use checksums |
ad568449fa77d6a202abada6d5905bcc3ac2212e244e96dec5acc788d2d8efca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 7, 2026.
Transparency logRelease files / python_check_updates-0.2.2-py3-none-any.whl
| Download URL | python_check_updates-0.2.2-py3-none-any.whl |
|---|---|
| Size | 10.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d88666754948e159dbb521ebf297e04b497894e3dfb684c17dd1c43b4c815ddc
|
|
BLAKE2b-256 checksum How to use checksums |
d3e478457b2306d399c048bf7ec0c163f0282d35e24b77957b9c7d6b4d9505a6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 7, 2026.
Transparency log