Universal changeset management tool for all programming languages and ecosystems.

Verset brings the developer experience of JavaScript's changesets to all programming languages. It supports both single repositories and monorepos, with first-class support for Rust, Python, Node.js, Go, Java, and .NET projects.

• 🌍 Universal Language Support - Works with any language that stores version numbers in parseable files
• 📦 Monorepo & Single-Repo - Handle complex monorepos with cross-package dependencies
• 🎯 Interactive CLI - User-friendly interface for creating changesets
• 📝 Automatic Changelog - Generate changelogs in Keep a Changelog format
• 🚀 Publishing Support - Publish packages to their respective registries
• ⚡ Fast & Reliable - Written in Rust for performance and reliability

cargo install verset

git clone https://github.com/yourusername/verset
cd verset
cargo install --path .

verset init

This will:

• Create .verset/ directory
• Generate config.toml with sensible defaults
• Auto-detect packages in your repository

# Interactive mode (recommended)
verset add

# Non-interactive mode
verset add --package my-package --type minor --message "Add new feature"

verset status

# Preview changes
verset apply --dry-run

# Apply changes
verset apply

verset publish

cd my-rust-project
verset init
verset add --type minor --message "Add OAuth support"
verset apply
verset publish

cd my-monorepo
verset init

# Add changeset for multiple packages
verset add --package "core,api" --type patch --message "Fix memory leak"

# Add changeset for all packages
verset add --all --type major --message "Breaking: Update API"

# Apply changes to specific package
verset apply --package core

# Publish specific packages
verset publish --package "core,api"

# GitHub Actions example
- name: Apply changesets
  run: |
    verset apply
    
- name: Publish packages
  if: github.ref == 'refs/heads/main'
  run: |
    verset publish
  env:
    CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_TOKEN }}
    NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

Verset uses a TOML configuration file located at .verset/config.toml.

[packages]
# Glob patterns for package discovery
patterns = ["packages/*", "apps/*", "."]

[changelog]
enabled = true
file = "CHANGELOG.md"
format = "keep-a-changelog"

[post_apply]
# Commands to run after applying changesets
commands = [
  "cargo check",
  "npm run build"
]

[[packages.manual]]
name = "my-package"
path = "packages/core"
type = "rust"
version_file = "Cargo.toml"
version_path = "package.version"

[publish.rust]
registry = "https://crates.io"
command = "cargo publish"

[publish.node]
registry = "https://registry.npmjs.org"
command = "npm publish"

[[publish.packages]]
name = "my-private-package"
commands = ["npm publish --registry https://npm.company.com"]

• Version file: Cargo.toml
• Version path: package.version
• Publish: cargo publish

• Version file: package.json
• Version path: version
• Publish: npm publish

• Version files: pyproject.toml, __init__.py
• Version paths: project.version, tool.poetry.version, __version__
• Publish: poetry publish

• Version file: go.mod, version.go
• Version detection: Looks for const Version = "x.y.z"
• Publish: go mod publish

• Maven: pom.xml
• Gradle: build.gradle, build.gradle.kts
• Publish: mvn deploy

• Version file: *.csproj
• Version path: Version
• Publish: dotnet nuget push

Changesets are stored as Markdown files in .verset/changesets/:

---
packages:
- my-package
- another-package
type: minor
---

Add OAuth2 authentication support

- Add Google and GitHub providers
- Update authentication middleware
- Add configuration options

Initialize verset in the current repository.

Create a new changeset.

Options:

• --package <PACKAGES> - Target specific package(s), comma-separated
• --type <TYPE> - Change type (major|minor|patch)
• --message <MESSAGE> - Change description
• --all - Apply to all packages

Show pending changesets and version impacts.

Options:

• --package <PACKAGE> - Show status for specific package

Apply pending changesets and update versions.

Options:

• --package <PACKAGE> - Apply only to specific package(s)
• --dry-run - Preview changes without applying
• --no-changelog - Skip changelog generation

Publish packages to their registries.

Options:

• --package <PACKAGES> - Publish specific package(s)
• --dry-run - Preview what would be published
• --registry <URL> - Override default registry

List all detected packages with their versions.

Validate configuration and package definitions.

Contributions are welcome! Please feel free to submit a Pull Request.

This project is licensed under the MIT License - see the LICENSE file for details.