Using the features available at zest.releser.lasttaglog this module fills the CHANGES file using the VCS’s log command.
Actual implementation only works with git. To add support to other VCSs you need to add new conditions to the prettyfy_logs method
Developing
Create a virtualenv somewhere:
$ virtualenv . $ source bin/activate
Install zc.buildout:
$ pip install zc.buildout
Run buildout:
$ ./bin/buildout -vv
Latest zest.releaser with the developing version of cs.zestreleaser.changelog will be installed and available through all the scripts created in bin folder. So you can run bin/fullrelease for instance.
Changelog
1.1 (2021-02-02)
Prettify svn log messages. [erral]
1.0.1 (2020-07-13)
Tag commands should be lists. [erral]
1.0 (2020-07-13)
Error control for missing tags [erral]
Change svn base class [erral]
0.8 (2020-02-24)
Changes due to changes in zest.releaser latest version [uodriozola]
0.7 (2015-10-02)
Unicode support for changelog entries [erral]
0.6 (2015-10-01)
Fix changelog update :(.
0.5 (2015-09-30)
fix history checking [Mikel Larreategi <mlarreategi@codesyntax.com>]
0.4 (2015-09-24)
use print as function [Mikel Larreategi <mlarreategi@codesyntax.com>]
get all commits when no tags are found [Mikel Larreategi <mlarreategi@codesyntax.com>]
documentation and buildout update [Mikel Larreategi <mlarreategi@codesyntax.com>]
hook changelog filler before the preleaser, because now zest.releaser checks for ‘not changes yet’ before the middle hook is run [Mikel Larreategi <mlarreategi@codesyntax.com>]
0.3 (2015-05-25)
Update import to be compatible with zest.releaser >= 4
0.2 (2014-12-12)
Show all the commits made since the last tag to the user before asking anything.
0.1 (2014-12-12)
Initial implementation: asks the user if he wants to add the last commits made since the last tag to the CHANGES file. This initial implementation works only with git.
1 maintainer
Metadata
1 maintainer
Release files for cs.zestreleaser.changelog 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 | Provenance | |
|---|---|---|---|---|
| cs.zestreleaser.changelog-1.1.tar.gz | 16.9 kB | Without provenance | Details |
Release files / cs.zestreleaser.changelog-1.1.tar.gz
| Download URL | cs.zestreleaser.changelog-1.1.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4a59271d9db9c0ee18a4fc21a66c8eeb4371261f3c5afb2e3e894e469fae9ac4
|
|
BLAKE2b-256 checksum How to use checksums |
fc7936785cd8ecd7da6b164e4bb3d81a62953578c8806c6effbc73751ea2c909
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/45.2.0 requests-toolbelt/0.9.1 tqdm/4.46.1 CPython/3.8.5
|
Security for cs.zestreleaser.changelog 1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
