rubrical
A CLI to encourage (😅) people to update their dependencies!
raison d'etre
Scenario: A team publishes an update to a new library that needs to be adopted.
(New feature, breaking changes, security fixes, etc)
Given your company has a microservice architecture
(or >3 repositories to update across >2 teams )
Then you go to each team and beg/bargin/plead for them to update their packages
You can (should!) use tools like renovate to automate dependency updates. But it's easy to lose track of updates especially with particularly technologies (hi JS/TS!) or busy teams.
rubrical breaks the cycle by putting a check inside your CI/CD pipelines. (Golden pipelines or shared workflows are highly recommended!) Now teams have a tool to automatically (automagically!) communicated when a dependency needs to be upgraded!
For more information, checkout the documentation!
Features
- Set warning (notify users their dependency will be out of date soon) and block (exit with error code) levels.
- Supports different languages (Python, Go, Node.js, and Jsonnet) and package manager formats (e.g. pip, poetry).
- Post results to Github/GHE PRs.
Metadata
Release files for rubrical 2.0.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 | |
|---|---|---|---|
| rubrical-2.0.0.tar.gz | 271.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| rubrical-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 298.2 kB
Release files / rubrical-2.0.0.tar.gz
| Download URL | rubrical-2.0.0.tar.gz |
|---|---|
| Size | 271.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9a1177332b2eab4d7c50b9f249b8d4fdc692c0b1b47b051d69eccc627d975d17
|
|
BLAKE2b-256 checksum How to use checksums |
ad0627107fae9a1c5b593e1290da65ae6d9adbae3c5a52dfdf8334b18db5d889
|
| 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 Jan 10, 2026.
Transparency logRelease files / rubrical-2.0.0-py3-none-any.whl
| Download URL | rubrical-2.0.0-py3-none-any.whl |
|---|---|
| Size | 26.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4f6ada0a5be2ebcd0532980623ef266a27326c5ee5c3de35bc06894bdc030df2
|
|
BLAKE2b-256 checksum How to use checksums |
9f1933c4a4bff85006fd5e18910ebd60fb9793a52838a1c358e74465c925250d
|
| 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 Jan 10, 2026.
Transparency log