One Updater
A flexible package manager updater that helps you keep all your development tools up to date.
Features
- Update multiple package managers with a single command
- Configure which package managers to update
- Support for virtual environments and pyenv for Python packages
- Beautiful command-line interface with rich formatting and logging
- Cross-platform support
- Extensible architecture for adding new package managers
Supported Package Managers
- Homebrew
- pip (with virtualenv/pyenv support)
- npm
- cargo
- gem
- pipx
- pacman
- dnf
- flatpak
- pkgx
- vagrant-plugins
- micro editor plugins
- tldr pages
- go packages
- apt
- bin (https://github.com/marcosnils/bin)
- More coming soon!
Installation
Install from PyPI:
pip install one-updater
To upgrade to the latest version:
pip install --upgrade one-updater
Use one of the pre-built executables in one_updater/bin e.g.:
sudo cp one-updater-linux /usr/local/bin/one-updater
sudo chmod +x /usr/local/bin/one-updater
Usage
Basic Usage
Update all enabled package managers:
one-updater update
Update specific package managers:
one-updater update -m homebrew -m pip
List configured package managers:
one-updater list-managers
Initialize a new configuration file:
one-updater init
Configuration
The tool uses a YAML configuration file (default: ~/.config/one-updater/config.yaml) to specify package manager settings. You can:
- Enable/disable specific package managers
- Configure virtualenv/pyenv for Python packages
- Customize update commands
- Configure logging and verbosity
Example configuration:
verbose: true
logging:
level: "INFO"
format: "%(message)s"
package_managers:
homebrew:
enabled: true
commands:
update: ["brew", "update"]
upgrade: ["brew", "upgrade"]
pip:
enabled: true
virtualenv: "/path/to/virtualenv" # Optional
pyenv: "3.11.0" # Optional
commands:
update: ["pip", "install", "--upgrade", "pip"]
upgrade: ["pip", "list", "--outdated", "--format=json"]
Contributing
Contributions are welcome! Feel free to:
- Add support for new package managers
- Improve error handling and logging
- Add new features
- Fix bugs
- Improve documentation
Please ensure your changes pass the test suite and code quality checks:
# Install development dependencies
poetry install
# Run tests
poetry run pytest
# Run code formatting
poetry run black .
License
MIT License
Metadata
Release files for one-updater 1.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| one_updater-1.4.0.tar.gz | 27.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| one_updater-1.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 62.0 kB
Release files / one_updater-1.4.0.tar.gz
| Download URL | one_updater-1.4.0.tar.gz |
|---|---|
| Size | 27.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eb668c9573eebf414a411d477a0e407b8f877fdfb487e786fa8896598f512c8e
|
|
BLAKE2b-256 checksum How to use checksums |
609a49aaf19939971c8a17ad6e9f41c5c7ac19f4f359bd0656021fff566c80f0
|
| 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 Sep 8, 2026.
Transparency logRelease files / one_updater-1.4.0-py3-none-any.whl
| Download URL | one_updater-1.4.0-py3-none-any.whl |
|---|---|
| Size | 34.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f99b3b60be7dd977d5b2d80786fb08eff7de5fd99029991ce6fb5f1e1d147647
|
|
BLAKE2b-256 checksum How to use checksums |
493cc0620ba0da497d2c48456bbc4ff6ccc2075bcdc8f4db5191b2829977a44c
|
| 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 Sep 8, 2026.
Transparency log