| Crates.io | workspyce |
| lib.rs | workspyce |
| version | 0.1.0 |
| created_at | 2025-12-13 20:30:45.00466+00 |
| updated_at | 2025-12-13 20:30:45.00466+00 |
| description | A minimal, no-nonsense version manager for uv workspaces, inspired by changesets |
| homepage | |
| repository | https://github.com/AstraBert/workspyce |
| max_upload_size | |
| id | 1983384 |
| size | 33,837 |
A minimal, no-nonsense version manager for uv workspaces, inspired by changesets.
Disclaimer: I am doing this to learn Rust! This might not be the most efficient way to manage versions in your uv workspace (at least no yet ;)
Please note that
workspycemight still have bugs and may produce inconsistent results
Install:
cargo install workspyce
Use the resulting build as an entrypoint:
./target/debug/workspyce --help
Use it within a python project:
workspyce check --pyproject pyproject.toml
The program should find the members within your uv workspace (should also compile with a regular expression for the * wildcard), check the current status of your git repository and ask for what kind of version bump you want to perform for a specific package, saving the info to a markdown file in the .workspyce/ folder.
workspyce version
This will remove all the markdown files and produce a .workspyce/release.txt file including the paths to all the files to release.
workspyce release --token YOUR_PYPI_TOKEN
This will remove the release.txt file and create a dist/ directory where the build outputs are stored for publication.