javachanges ​

javachanges is a release-planning CLI for Maven and Gradle repositories.

The workflow is intentionally simple:

1. contributors record intended changes in .changesets/*.md
2. CI or maintainers inspect a generated release plan
3. the plan updates the root version and changelog
4. CI publishes with Maven deploy or Gradle-native publishing tasks

The tool stays file-centric. It does not require a database or a hosted service.

Release flow at a glance ​

Core ideas ​

• Keep release intent in versioned files.
• Review release plans before publishing.
• Generate changelogs from structured Changesets-compatible metadata.
• Avoid shell-heavy release logic where possible.

What the CLI assumes ​

• a Maven repository with a root pom.xml, or a Gradle repository with gradle.properties
• Maven <modules>, Gradle include(...) entries, or a single root artifact/project
• a root Maven revision or Gradle version property used for versioning
• a .changesets/ directory to store release notes-in-progress

Guides ​

• LLM Access
• Getting Started
• Maven Usage Guide
• Gradle Usage Guide
• Examples Guide
• Command Cookbook
• Configuration Reference
• CLI Reference
• Development Guide
• Release Plan Manifest
• Output Contracts
• Troubleshooting Guide
• Cloudflare Workers Builds
• GitHub Actions Release Flow
• GitHub Actions Usage Guide
• GitLab CI/CD Usage Guide
• Publish To Maven Central
• Use Cases