After the next version is determined and dry-run is confirmed off,
release.env is written to the repository root:
NEXT_VERSION=<nextTag>
This file is not committed — it is left as an untracked artifact so
GitLab CI can expose it as a dotenv artifact and pass NEXT_VERSION to
downstream jobs (e.g. deploy, notify).
The file is skipped in --dry-run mode. Two tests added:
TestRunReleaseEnv and TestRunReleaseEnvDryRun.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Tags are now bare version numbers by default (e.g. 1.2.3).
Set tag_prefix: "v" in .releaser.yml or pass --tag-prefix v to opt in
to the v-prefixed convention.
Updated all affected tests, the .releaser.yml template comment, and
the README configuration reference.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Adds a logHeader() helper that prints "releaser v<version>" to stderr
at the start of every invocation, before any other output.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Prints a configuration table on startup showing each key, its value,
and the source (default / config file / env: VARNAME / flag: --name)
- Lists every commit since the last tag with its parsed type and
the version-bump decision (feat/fix/breaking → patch bump, or ignored)
- Explains the final version choice: highest commit type → next tag
- All verbose output goes to stderr so it never pollutes stdout captures
- Sources tracking wired through config.LoadWithSources and
ApplyEnvWithSources; LoadWithSources uses a two-pass approach to
detect which YAML fields were explicitly set vs defaulted
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- Automatically write/update CHANGELOG.md on every release, grouped by
Breaking Changes / Added / Fixed; file is created if missing and the
new section is committed alongside pom.xml in the release commit
- Add --init flag: scaffolds a default .releaser.yml in the repo root
- Add --changelog-file flag: override the default CHANGELOG.md path
- Add CommitFiles() to gitutil so pom.xml and CHANGELOG.md are staged
in a single commit
- Fix HTTPS push when no token is set: delegate to the git CLI so that
system credential helpers, SSH agents, and netrc are honoured
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Pushes the commit and tag as normal but exits before calling the GitLab
API. Useful when the project is hosted on a non-GitLab forge (e.g.
Gitea) where the release is handled by a separate CI workflow triggered
on the tag push.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
If pom.xml (or the configured maven.pom_path) is absent, releaser now
logs a notice and proceeds to tag and push without failing. This makes
the tool usable in non-Maven projects. An os.Stat error that is not
ErrNotExist (e.g. permission denied) still surfaces as an error.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
k3nny