Not getting merged
ChangeLog and Release Management Tooling
A simple standalone Python module for CHANGELOG and release management. Spun out of octoDNS.
Installation
Command line
pip install changelet
Usage
For help with using the command
changelet --help
In most cases the only command you're likely to encounter is create. It will be used to add a changelog entry to your branch/PR.
changelet create --type (TYPE) Short description of your change to be included in the changelog
The options for type are
major- rare for non-maintainers, a change that will break backwards compatibility and require users to take care when updatingminor- adds new functionality that is either self contained or done in a completely backwards compatible mannerpatch- fixes an issue or bug with existing functionalitynone- change that should not be included in the CHANGELOG and will not directly impact users, e.g. documentation, README, tooling, ...
Slash Command
There is an optional GitHub slash command action that can installed. If it's installed users with write permissions to the repo can add a comment in the PR to add Changelog entries. The interface is almost idential to the command line, though only the create command is supported at this time.
/changelog create -t none This is an example changelog entry added as a PR comment
Using changlet
Currently the tooling has only been tested with repositories in the octoDNS org, but it should be usable elsewhere. You'll want to have a look at the following for how to incorporate it into your repo and workflows.
- (octodns) script/changelog
- .git_hooks_pre-commit (and script/bootstrap which installs it)
- .github/workflows/changelog.yml
Development
See the /script/ directory for some tools to help with the development process. They generally follow the Script to rule them all pattern. Most useful is ./script/bootstrap which will create a venv and install both the runtime and development related requirements. It will also hook up a pre-commit hook that covers most of what's run by CI.
Metadata
Release files for changelet 0.6.1
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 | |
|---|---|---|---|---|
| changelet-0.6.1.tar.gz | 25.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| changelet-0.6.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.0 kB
Release files / changelet-0.6.1.tar.gz
| Download URL | changelet-0.6.1.tar.gz |
|---|---|
| Size | 25.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4e33ce4033d23827c53deabb71003bcf6ddc98a18334a202cde55dc985c4c52
|
|
BLAKE2b-256 checksum How to use checksums |
a3cd03fd2b613790df41e3277dfe7115e3c1476635898f15e6f6df21d8a94ce1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Release files / changelet-0.6.1-py3-none-any.whl
| Download URL | changelet-0.6.1-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3f3b94727fd37116488b749626706eb7eed12650e29f684f4b59ad05484bec0f
|
|
BLAKE2b-256 checksum How to use checksums |
2adb903b171a71cbeefb4ef378cabfcb7d4b0fe14ec156ae40cb0cf713822e12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.13
|
Security for changelet 0.6.1
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.