This release is a pre-release and may not be stable for production use.
Verlato
Release notes you can trust, drafted from what your code actually changed.
Verlato reads the commits between two refs, groups them into pull-request-sized changesets,
works out what each one did, and drafts a changelog entry and GitHub release notes for you to
review and apply. It is powered by the IntentumDiff
semantic diff engine: every commit is reviewed structurally, so Verlato knows whether a change
is behavioural, additive, a refactoring or move, or formatting only, and which functions,
methods and classes were added, removed, renamed or re-signatured. A vague wip commit that
renames a public function is flagged as a possible breaking change.
Use it from the command line, the VS Code extension or any MCP client. Models are optional and local by default; they see the semantic diff, never your raw patches, unless you allow it.
Documentation: https://buchochelliq-labs.github.io/verlato-core/
Powered by IntentumDiff (docs) and your agent. IntentumDiff supplies the evidence: what each commit actually changed. Your agent supplies the words: Claude Code, Codex, GitHub Copilot or any other MCP client, or a model of your choice, local by default.
Install
Verlato 0.2.0-beta.1 is a pre-release, so installers need to be told to accept it:
pip install --pre verlato-core # CPython 3.12+; Linux, macOS, Windows (PyPI: 0.2.0b1)
The VS Code extension is on the Visual Studio Marketplace and Open VSX as a Pre-Release version: choose Switch to Pre-Release Version on its page (or Install Pre-Release).
Or download a self-contained bundle (the verlato executable plus its parser bundle) for your
platform from GitHub Releases, or
build from source.
The VS Code extension is in vscode-extension/.
Quickstart
From inside a git repository with at least one tag:
verlato draft preview --from-latest-tag --version v1.1.0
Then review the items, apply the notes, and record the release:
verlato draft json --from-latest-tag # items, evidence, semantic review
verlato draft review --from-latest-tag --id <item-id> --status accepted --summary "..."
verlato draft apply --from-latest-tag --version v1.1.0 --target changelog
git tag -a v1.1.0 -m v1.1.0
verlato generate --base <previous-tag> --head v1.1.0
verlato state mark-published --version v1.1.0 --all-unpublished
Want better wording? Run a local Ollama model and try
verlato draft suggest --from-latest-tag --all-visible --preview.
Learn more
- Getting started
- User guide: the command line, the VS Code extension, models, privacy modes, the MCP server
- Reference: CLI,
verlato.json, environment variables, Python API - Technical guide: architecture, semantic evidence, extension points
The documentation's source is in docs/; build it with
pip install zensical==0.0.74 && zensical build --strict.
Contributing
See CONTRIBUTING.md. In short: cargo test --workspace, pytest (after
pip install -e '.[dev]') and npm test in vscode-extension/.
License and open core
Verlato is licensed under the Apache License, Version 2.0; see also NOTICE. Releases before the relicensing were published under the MIT License.
Verlato is open core: everything one developer needs is here and free. Team and organisation features are built separately on core's public extension points; see Open core.
Metadata
Release files for verlato-core 0.2.0b1
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 |
|---|---|---|---|---|
| verlato_core-0.2.0b1.tar.gz | 12.0 MB | With provenance | Details for verlato_core-0.2.0b1.tar.gz |
Built distributions (wheels)
| File | Actions Reset | |||
|---|---|---|---|---|
| verlato_core-0.2.0b1-cp312-abi3-win_amd64.whl | CPython 3.12 | abi3 | Windows x86-64 | Details for verlato_core-0.2.0b1-cp312-abi3-win_amd64.whl |
| verlato_core-0.2.0b1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.17+ x86-64 | Details for verlato_core-0.2.0b1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
| verlato_core-0.2.0b1-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.17+ ARM64 | Details for verlato_core-0.2.0b1-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
| verlato_core-0.2.0b1-cp312-abi3-macosx_11_0_arm64.whl | CPython 3.12 | abi3 | macOS 11.0+ ARM64 | Details for verlato_core-0.2.0b1-cp312-abi3-macosx_11_0_arm64.whl |
| verlato_core-0.2.0b1-cp312-abi3-macosx_10_12_x86_64.whl | CPython 3.12 | abi3 | macOS 10.12+ x86-64 | Details for verlato_core-0.2.0b1-cp312-abi3-macosx_10_12_x86_64.whl |
Total release size: 137.8 MB
Release files / verlato_core-0.2.0b1.tar.gz
| Download URL | verlato_core-0.2.0b1.tar.gz |
|---|---|
| Size | 12.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
558ae0b832462410ea7180974e2f4a1d5c36b193f8b5b525ddba6b27dfc4e58a
|
|
BLAKE2b-256 checksum How to use checksums |
eae3a3751898dbecbf1615997c6611d0d5feaa3de57f3ae40acaa433f46a62ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logRelease files / verlato_core-0.2.0b1-cp312-abi3-win_amd64.whl
| Download URL | verlato_core-0.2.0b1-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 26.2 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
710aa8fa8986ab33e0aca08995c4c9f5418919b1e5d6c21a1b3563ff058869a2
|
|
BLAKE2b-256 checksum How to use checksums |
dee56aaabeb3c8f4a80adac6fe089e4c74fbb64ba27f9d773595917e7a6e32ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logRelease files / verlato_core-0.2.0b1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
| Download URL | verlato_core-0.2.0b1-cp312-abi3-manylinux2014_x86_64.manylinux_2_17_x86_64.whl |
|---|---|
| Size | 26.0 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
551972adfc1530d72653dfadebf5e6365ffbe6871df8a6fc816f82ea5df8c380
|
|
BLAKE2b-256 checksum How to use checksums |
0ade332a17fede37ea6b5dd89ef12292c78a56d1f5d3a5c378a4149f476db782
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logRelease files / verlato_core-0.2.0b1-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl
| Download URL | verlato_core-0.2.0b1-cp312-abi3-manylinux2014_aarch64.manylinux_2_17_aarch64.whl |
|---|---|
| Size | 24.5 MB |
| Tags | CPython 3.12 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
5dc0b8bd6a6cc85e80360f4489f581ff87569ccf5d9b4ba22a5d8842b60719c8
|
|
BLAKE2b-256 checksum How to use checksums |
cdf7801aeb743e69be23f37eb97dfe9a228913b17c1ee60f72f43e46c4eef0fd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logRelease files / verlato_core-0.2.0b1-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | verlato_core-0.2.0b1-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 24.0 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
1db9f4b7eb1297f44575b43030dd4b4614552622549c017b7cadeb8b2970a699
|
|
BLAKE2b-256 checksum How to use checksums |
8cf83c35f89bb8268b966ebda4af8a7adb91d599348e276cd0ed008248429064
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logRelease files / verlato_core-0.2.0b1-cp312-abi3-macosx_10_12_x86_64.whl
| Download URL | verlato_core-0.2.0b1-cp312-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 25.2 MB |
| Tags | CPython 3.12 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
d46bfb5016e2c075d51fcd662f3caf9cbf4c955d4cfe889342fdafa5960bfd5f
|
|
BLAKE2b-256 checksum How to use checksums |
7fb39d2f2c1bd4b0843033960f1daec1b76887af6032411b7b245d025e4d008f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.12.16
|
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 Nov 19, 2026.
Transparency logSecurity for verlato-core 0.2.0b1
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.
Full provenance
All 6 files in this release have been uploaded with provenance metadata.
Attestation for verlato_core-0.2.0b1.tar.gz
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 Nov 19, 2026.
Transparency logA 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.