changelogs

A Rust rewrite of changesets for Cargo workspaces.

Installation

cargo install changelogs

Quick Start

# Initialize changelogs in your workspace
changelogs init

# Add a changelog for your changes
changelogs add

# See what would be released
changelogs status

# Apply version bumps and generate changelogs
changelogs version

Workflow

1. Make changes to your code
2. Run changelogs add to describe your changes
3. Commit the changelog file with your PR
4. Merge your PR
5. Run changelogs version (or let the GitHub Action do it)
6. Merge the "Version Packages" PR

Commands

Configuration

.changelog/config.toml:

# How to bump packages that depend on changed packages
dependent_bump = "patch"  # patch, minor, or none

[changelog]
format = "per-crate"  # or "root"

# Fixed groups: all always share the same version
[[fixed]]
members = ["crate-a", "crate-b"]

# Linked groups: versions sync when released together  
[[linked]]
members = ["sdk-core", "sdk-macros"]

# Packages to ignore
ignore = []

Changelog Format

.changelog/brave-lions-dance.md:

---
my-crate: minor
other-crate: patch
---

Added new feature X that does Y.

Fixed bug Z in the parser.

GitHub Action

name: Release

on:
  push:
    branches: [main]

jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: dtolnay/rust-toolchain@stable
      - run: cargo install changelogs
      - uses: wevm/changelogs-rs@v1
        with:
          version: changelogs version
          publish: changelogs publish
          crate-token: ${{ secrets.CARGO_REGISTRY_TOKEN }}
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The action automatically handles both versioning and publishing:

1. If changelogs exist → Creates/updates a "Version Packages" PR
2. If no changelogs (PR was just merged) → Publishes unpublished packages to crates.io

Action Inputs

Action Outputs

License

MIT OR Apache-2.0