Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ivanklee86/rubrical
A CLI to encourage (😅) people to update their dependencies!
https://github.com/ivanklee86/rubrical
cicd dependencies
Last synced: about 2 months ago
JSON representation
A CLI to encourage (😅) people to update their dependencies!
- Host: GitHub
- URL: https://github.com/ivanklee86/rubrical
- Owner: ivanklee86
- License: mpl-2.0
- Created: 2022-12-02T23:30:05.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2024-05-21T11:42:03.000Z (7 months ago)
- Last Synced: 2024-05-22T11:46:50.106Z (7 months ago)
- Topics: cicd, dependencies
- Language: Python
- Homepage: https://ivanklee86.github.io/rubrical/
- Size: 1.14 MB
- Stars: 2
- Watchers: 1
- Forks: 2
- Open Issues: 6
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# rubrical
[![CI](https://github.com/ivanklee86/rubrical/actions/workflows/ci.yaml/badge.svg)](https://github.com/ivanklee86/rubrical/actions/workflows/ci.yaml) [![codecov](https://codecov.io/gh/ivanklee86/rubrical/branch/main/graph/badge.svg?token=9WJM4LBDEX)](https://codecov.io/gh/ivanklee86/rubrical) [![PyPI version](https://badge.fury.io/py/rubrical.svg)](https://badge.fury.io/py/rubrical)
A CLI to encourage (😅) people to update their dependencies!
## raison d'etre
```gherkin
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](https://github.com/renovatebot/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](https://ivanklee86.github.io/rubrical/)!
## 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.![rubrical](https://github.com/ivanklee86/rubrical/blob/main/docs/images/rubrical.png?raw=true)