fix(maven): skip pom.xml update when file does not exist

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>
2026-07-07 00:33:57 +02:00
parent c92164eb37
commit 7fdf5ddcf3
4 changed files with 47 additions and 9 deletions
@@ -3,11 +3,12 @@
 All notable changes to this project will be documented in this file.
 Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).

-## [0.4.1] - 2026-07-07
+## [0.4.2] - 2026-07-07

 ### Fixed

 - **CI build step** — `go build ./cmd/...` failed with "output already exists and is a directory" because Go tried to write a binary named `cmd`, conflicting with the source directory; fixed by passing `-o /dev/null`
+- **Optional pom.xml** — releaser no longer fails when `pom.xml` (or the configured `maven.pom_path`) does not exist; it logs a notice and proceeds directly to tag and push, making the tool usable in non-Maven projects

 ## [0.4.0] - 2026-07-07