once.releaser
Custom releaser hooks for JIRA project based on zest.releaser and cs.zestreleaser.changelog. This hook extract the commit messages from the last release tag to the current tag and create the towncrier news fragments, based on the JIRA issue and the towncrier type.
Currently it only supports GIT VCS logs.
The commit messages must be in the following format:
<optional prefix> <issue_name>-<issue_number> <towncrier type> <message> [<author>]
Author will be extracted from the git history.
Examples
The following commit messages are valid:
Revert WEBAGL-1234 feature Add new feature
Add WEBAGL-1234 feature new feature
WEBAGL-1235 bugfix Fix AttributeError RequestContainer object has no attribute getClientForURL
Fragments files will be created in the following format:
news/WEBAGL-1234.feature
Add new feature [Rafael Bermúdez Horcajada <myemail@email.com>] Revert new feature [Rafael Bermúdez Horcajada <myemail@email.com>]
news/WEBAGL-1235.bugfix
Fix AttributeError RequestContainer object has no attribute getClientForURL [Rafael Bermúdez Horcajada <myemail@email.com>]
Installation
Using pip:
$ pip install once.releaser
Contributors
Put your name here, you deserve it!
?
Contribute
Issue Tracker: https://github.com/once.releaser/issues
Source Code: https://github.com/once.releaser
License
The project is licensed under the GPLv2.
Changelog
1.1 (2025-04-11)
Bug fixes:
Fix dependency name (internal)
1.0 (2025-04-11)
No significant changes.
1.0a10 (2024-09-30)
Bug fixes:
Extract commits ignoring merged [Bermúdez Horcajada, Rafael] (#1)
1.0a9 (2024-09-24)
Bug fixes:
Fix duplicate entries
1.0a8 (2024-09-20)
New features:
Git add after all files are updated.
1.0a7 (2024-09-20)
Bug fixes:
Ensure the newsfile is added to the git index to avoid pre-commit hooks to fail
1.0a6 (2024-09-20)
Bug fixes:
Don’t assign encoding to file
1.0a5 (2024-09-20)
New features:
Execute at hook zest.releaser.prereleaser.before
1.0a4 (2024-09-20)
Bug fixes:
Fix regex pattern to extract prefix properly [Rafael Bermúdez Horcajada <rber474@gmail.com>]
1.0a3 (2024-09-19)
Bug fixes:
Fix release workfloww [Rafael Bermúdez Horcajada <rber474@gmail.com>]
1.0a2 (2024-09-19)
New features:
Switch to OpenID Connect [Rafael Bermúdez Horcajada <rber474@gmail.com>]
1.0a1 (unreleased)
Initial release. [rber474]
1 maintainer
Metadata
1 maintainer
Release files for once.releaser 1.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 | |
|---|---|---|---|
| once_releaser-1.1.tar.gz | 15.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| once_releaser-1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 29.8 kB
Release files / once_releaser-1.1.tar.gz
| Download URL | once_releaser-1.1.tar.gz |
|---|---|
| Size | 15.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6a80ec64d4eaa156c9d848ede4741118819cb2c7f0f215627bccbbe703978693
|
|
BLAKE2b-256 checksum How to use checksums |
9009f9184ab2cfb279152aaa609afddd2ffa7d038cef9a9c06f2bc39cf8e5a2d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 11, 2025.
Transparency logRelease files / once_releaser-1.1-py3-none-any.whl
| Download URL | once_releaser-1.1-py3-none-any.whl |
|---|---|
| Size | 14.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0e88c1639ec53a4772fca73776c72ed349d72b3efc2ab5be0190af935f915345
|
|
BLAKE2b-256 checksum How to use checksums |
398454ec3dc66b979e44d9f3ab89a32a5dc54368bd6dfcff83c490aa4c5cddc4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
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 Apr 11, 2025.
Transparency log
