Simple changelog parser, written in Rust.
sh
cargo install parse-changelog
You can download prebuilt binaries from the Release page. Prebuilt binaries are available for macOS, Linux (gnu and musl), and Windows (static executable).
You can install parse-changelog using Homebrew tap on macOS and Linux:
sh
brew install taiki-e/tap/parse-changelog
You can install parse-changelog using Scoop:
sh
scoop bucket add taiki-e https://github.com/taiki-e/scoop-bucket
scoop install parse-changelog
You can install parse-changelog using cargo-binstall:
sh
cargo binstall parse-changelog
You can install parse-changelog from the MPR:
sh
git clone 'https://mpr.makedeb.org/parse-changelog'
cd parse-changelog/
makedeb -si
You can also install parse-changelog from the Prebuilt-MPR, which provides automatic upgrades directly via APT. First set up the Prebuilt-MPR on your system, and then run the following:
sh
sudo apt install parse-changelog
Note: The MPR/Prebuilt-MPR packages are maintained by the community, not the maintainer of parse-changelog.
You can use taiki-e/install-action to install prebuilt binaries on Linux, macOS, and Windows. This makes the installation faster and may avoid the impact of problems caused by upstream changes.
yaml
- uses: taiki-e/install-action@parse-changelog
To use this crate as a library, add this to your Cargo.toml:
toml
[dependencies]
parse-changelog = { version = "0.4", default-features = false }
Note: When using this crate as a library, we recommend disabling the default features because the default features enable CLI-related dependencies and the library part of this crate does not use them.
Compiler support: requires rustc 1.56+
parse-changelog command parses changelog and returns a release note for the
specified version.
Click to show a complete list of options
```console $ parse-changelog --help parse-changelog
Simple changelog parser, written in Rust.
Parses changelog and returns a release note for the specified version.
USAGE:
parse-changelog [OPTIONS]
ARGS:
OPTIONS:
-t, --title Returns title instead of notes
--json Returns JSON representation of all releases in changelog
--version-format
Get the release note for version 1.46.0 from Rust's release notes:
sh
curl -fsSL https://raw.githubusercontent.com/rust-lang/rust/master/RELEASES.md \
| parse-changelog - 1.46.0
In Cargo's changelog,
the title starts with "Cargo ", and the patch version is omitted. This is a
format parse-changelog don't support by default, so use --prefix and
--version-format to specify a custom format. For example:
sh
curl -fsSL https://raw.githubusercontent.com/rust-lang/cargo/master/CHANGELOG.md \
| parse-changelog --prefix 'Cargo ' --version-format '^[0-9]+\.[0-9]+$' - 1.50
--prefix is the same as [Parser::prefix_format] and --version-format is
the same as [Parser::version_format]. See documentation of those methods for
more information.
With GitHub CLI:
```sh tag=... version=...
notes=$(parse-changelog CHANGELOG.md "$version")
gh release create "$tag" --title "$version" --notes "$notes" ```
See also [create-gh-release-action].
```rust let changelog = "\
Foo.Bar.Initial release ";
// Parse changelog. let changelog = parse_changelog::parse(changelog).unwrap();
// Get the latest release. asserteq!(changelog[0].version, "0.1.2"); asserteq!(changelog[0].title, "0.1.2 - 2020-03-01"); assert_eq!(changelog[0].notes, "- Bug fixes.");
// Get the specified release.
asserteq!(changelog["0.1.0"].title, "0.1.0 - 2020-01-01");
asserteq!(changelog["0.1.0"].notes, "Initial release");
asserteq!(changelog["0.1.1"].title, "0.1.1 - 2020-02-01");
asserteq!(
changelog["0.1.1"].notes,
"- Added Foo.\n\
- Added Bar."
);
```
See documentation for more information on
parse-changelog as a library.
By default, this crate is intended to support markdown-based changelogs that have the title of each release starts with the version format based on Semantic Versioning. (e.g., Keep a Changelog's changelog format.)
The heading for each release must be Atx-style (1-6 #) or
Setext-style (= or - in a line under text), and the heading levels
must match with other releases.
Atx-style headings:
```markdown
```
```markdown
```
Setext-style headings:
```markdown
```
```markdown
```
The title of each release must start with a text or a link text (text with
[ and ]) that starts with a valid version format or
prefix format. For example:
```markdown
description...
description... ```
You can include characters before the version as prefix.
```text
^^^^^^^^ ```
By default only "v", "Version ", "Release ", and "" (no prefix) are allowed as prefixes.
To customize the prefix format, use the [Parser::prefix_format] method (library) or --prefix-format option (CLI).
```text
^^^^^
```
The default version format is based on Semantic Versioning.
This is parsed by using the following regular expression:
text
^(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)(-[0-9A-Za-z\.-]+)?(\+[0-9A-Za-z\.-]+)?$|^Unreleased$
Note: To get the 'Unreleased' section in the CLI, you need to explicitly specify 'Unreleased' as the version.
To customize the version format, use the [Parser::version_format] method (library) or --version-format option (CLI).
You can freely include characters after the version.
```text
^^^^^^^^^^^^^
```
Licensed under either of Apache License, Version 2.0 or MIT license at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.