updee
Stupidly simple repo updater.
A CLI for keeping repos up to date, similar in spirit to updatecli, dependabot, and renovate.
Note: updee assumes you have the necessary programs installed (like npm, uv, etc.).
If not, it will give you a helpful error message.
Alternatively, use the docker image, which has all the tools installed.
Note: updee does not attempt to be a SaaS solution, chatbot, slack bot, GitHub PR bot.
It is simply a CLI which updates dependencies and commits those changes with nice commit messages.
The rest is left up to you, like when / where to run it and how to create pull requests.
It assumes you run it somewhere that makes those things easy for you (Such as in a GitHub Action).
Docker
The Dockerfile builds an image with upd and the CLIs it relies on (uv).
Build it once, then run upd in any repo / folder by mounting it at /repo:
docker build -t updee .
docker run --rm --user "$(id -u):$(id -g)" -v "$PWD:/repo" updee
Development
This project uses uv.
To run updee in this repo without installing it:
uv run updee
Development
Run formatting, linting, and tests:
make check
Metadata
Release files for updee 0.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| updee-0.0.1.tar.gz | 33.4 kB | With provenance | Details for updee-0.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| updee-0.0.1-py3-none-any.whl | Python 3 | none | any | Details for updee-0.0.1-py3-none-any.whl |
Total release size: 40.4 kB
Release files / updee-0.0.1.tar.gz
| Download URL | updee-0.0.1.tar.gz |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58c4da740ae3506ef6d142fa36f00701eb7985fcbeb6d8e02ea51fcfbfdb3991
|
|
BLAKE2b-256 checksum How to use checksums |
d5ac5c593a373fa55c81ee3dfbce4feae33294b04815cfd6549f1ddf63d2f39d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jul 16, 2026.
Transparency logRelease files / updee-0.0.1-py3-none-any.whl
| Download URL | updee-0.0.1-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f3bf527db0ce2545172762bed9594ce03717e369960c7877ae48fc7abf5bd9b
|
|
BLAKE2b-256 checksum How to use checksums |
3a0ab87aa231ca62c7072409d1b140812c0699ff5f1c3f3a150c84310ee1961a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Jul 16, 2026.
Transparency logSecurity for updee 0.0.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for updee-0.0.1.tar.gz
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 Jul 16, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.