Yaclog

Latest version: v1.2.0

Safety actively analyzes 638430 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

1.0.2

Changed

- Updated to support Click version 8
- Modified module documentation page titles to include a module role

Fixed

- Fixed tag names with spaces in versions

1.0.1

Fixed

- Fixed broken header in new changelogs
- Improved consistency in command documentation metavars

1.0.0

Changed

- API changes:
- `header` attribute renamed to `preamble` to avoid confusion.
- improved version header parsing to be more robust and handle multi-word version names.
- improved version number incrementing in `release`.
- can now handle other text surrounding a pep440-compliant version number, which will not be modified
- can now handle pre-releases correctly. The version to increment is the most recent version in the log with a valid pep440 version number in it.
- Release increment and prerelease increments can be mixed, allowing e.g: `yaclog release -mr` to create a release candidate with in incremented minor version number.
- `release` base version is now an argument instead of an option, for consistency with other commands.

Removed

- `entry` with multiple `-b` options no longer add sub bullet points, instead adding each bullet as its own line.

Added

- Terminal output has color to distinguish version names/headers, sections, and git information.
- Extra newlines are added between versions to improve readability of the raw markdown file.

0.3.3

Added

- Unit tests in the `tests` folder

Fixed

- Default links and dates in VersionEntry are now consistently `None`
- Changelog links dict now contains version links. Modified version links will overwrite those in the table when writing to a file
- Changelog object no longer errors when creating without a path.
- `release` now resets lesser version values when incrementing
- `release` now works with logs that have only unreleased changes

0.3.2

Added

- Readme file now has installation and usage instructions.
- yaclog command entry point added to setup.cfg.

Changed

- `release -c` will no longer create empty commits, and will use the current commit instead.

Fixed

- `release` and `entry` commands now work using empty changelogs.

0.3.1

Added

- `yaclog` tool for manipulating changelogs from the command line
- `init` command to make a new changelog
- `format` command to reformat the changelog
- `show` command to show changes from the changelog
- `entry` command for manipulating entries in the changelog
- `tag` command for manipulating tags in the changelog
- `release` command for creating releases

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.