recite
recite intends to make releasing poetry-based libraries easier and avoid missing important steps (e.g. adapting the changelog (because you should keep one)).
$ recite release patch
recite > 👀 Checking everything to make sure you are ready to release 👀
recite > 1: ✓ Make sure you have a (non-empty) pyproject.toml
recite > 2: ✓ Make sure you're on main/master branch
recite > 3: ✓ Make sure git is clean
recite > 4: ✓ Run test-suite
recite > 5: ✓ Make sure changelog was updated
recite > 🤓 Everything looks perfect! 🤓
recite > I will perform the following steps:
recite > * Would bump version from 0.1.0 to 0.1.1
recite > * Commit version bump
recite > * Create git tag 0.1.1
recite > * Push git tag 0.1.1
recite > * Remind you to upload build as github release
Do you want to proceed? [y/N]: y
recite > ✨ Performing release ✨
recite > 1: ✓ Bump version
recite > * Bumped version from 0.1.0 to 0.1.1
recite > 2: ✓ Commit version bump
recite > 3: ✓ Create git tag 0.1.1
recite > 4: ✓ Push git tag 0.1.1
recite > 5: ✓ Build and publish with poetry
Please create a github release now! Did you do it? [y/N]: y
recite > 6: ✓ Remind you to upload build as github release
recite > 🚀 Congrats to your release! 🚀
Installation
Since recite is a python application it is recommended to install it via pipx:
$ pipx install recite
But you can also install it via pip:
$ pip install recite
Usage
You can perform e.g a patch release with the command:
$ recite release patch
The classifiers are the same as poetry's bump rules of the it's version command.
To list the available checks use:
$ recite list-checks
You can find more info in the docs
Why?
Previously I used a github action to automatically build and publish a new version of a library if a new tag was pushed. However, sometimes I forgot something crucial (e.g. to adapt the changelog). In this case I had to rush to stop the github action before it would publish the release to pypi (where it would lie forever unable to be rectified).
With recite it is ensured all the necessary checks are in place before any tags are created.
Metadata
Release files for recite 0.2.2
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 | Actions |
|---|---|---|---|---|
| recite-0.2.2.tar.gz | 10.3 kB | Without provenance | Details for recite-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| recite-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for recite-0.2.2-py3-none-any.whl |
Total release size: 20.0 kB
Release files / recite-0.2.2.tar.gz
| Download URL | recite-0.2.2.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
da974460d71ec680dbf7e725554ea9e044effee23b6cb5522f3a4d4ba31632b9
|
|
BLAKE2b-256 checksum How to use checksums |
7540e82cb990ac2ba4a23d76272ab333f3c9a18c1acaccb7a60955c90689ffc2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.10.6 Linux/5.19.0-35-generic
|
Release files / recite-0.2.2-py3-none-any.whl
| Download URL | recite-0.2.2-py3-none-any.whl |
|---|---|
| Size | 9.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3a86dd05cba93324c1bf3a3a0b1a50047dda32097476642994b55d174389c5cc
|
|
BLAKE2b-256 checksum How to use checksums |
06dbc72f9ef3d0b48e80b89e8cf643d981129b4c4d746d693d56829ff78f5f90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.1 CPython/3.10.6 Linux/5.19.0-35-generic
|
Security for recite 0.2.2
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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.