Requirement Compare
A CLI that generate a version changelog based on git history and local requirement file.
Installation
pip install --upgrade pip
pip install requirement-compare
Usage
$ requirement-compare requirements.txt
- Added `last_package` version `1.0.0`
- Bump `example_package` from `1.0.0` to `2.0.0`
- Removed `another_package` version `1.0.0`
Metadata
Release files for requirements-compare 0.2.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 | Provenance | |
|---|---|---|---|---|
| requirements_compare-0.2.0.tar.gz | 10.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| requirements_compare-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.4 kB
Release files / requirements_compare-0.2.0.tar.gz
| Download URL | requirements_compare-0.2.0.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a6c2915ebc5c7678a7133c6f929560c3efe3d73588f07e537e16d771b22fe6d5
|
|
BLAKE2b-256 checksum How to use checksums |
4987f2dc7aa81dddac87adba12dbaa9ee02c54f6051f5c630355eae27f879cbc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Release files / requirements_compare-0.2.0-py3-none-any.whl
| Download URL | requirements_compare-0.2.0-py3-none-any.whl |
|---|---|
| Size | 5.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce934413138b12306c3a48fb4e37c8de48601c88c57a16ef004372f07724f97c
|
|
BLAKE2b-256 checksum How to use checksums |
95a65d188742d497a431f2947b7d1ed0185f839a39bce599d9a6b09a7848d90b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.4
|
Security for requirements-compare 0.2.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.