fix(ci): fix build step output path conflict
ci / vet, staticcheck, test, build (push) Successful in 2m47s

go build ./cmd/... tried to write a binary named "cmd" which conflicts
with the source directory of the same name; pass -o /dev/null so the
build step only verifies compilation without writing output.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-07-07 00:18:04 +02:00
parent f0723e706a
commit c92164eb37
3 changed files with 8 additions and 2 deletions
+1 -1
View File
@@ -37,4 +37,4 @@ jobs:
run: go test ./... run: go test ./...
- name: build - name: build
run: go build ./cmd/... run: go build -o /dev/null ./cmd/...
+6
View File
@@ -3,6 +3,12 @@
All notable changes to this project will be documented in this file. All notable changes to this project will be documented in this file.
Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Format: [Keep a Changelog](https://keepachangelog.com/en/1.1.0/).
## [0.4.1] - 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`
## [0.4.0] - 2026-07-07 ## [0.4.0] - 2026-07-07
### Added ### Added
+1 -1
View File
@@ -1,6 +1,6 @@
# releaser # releaser
![release](https://img.shields.io/badge/release-v0.4.0-blue.svg) ![release](https://img.shields.io/badge/release-v0.4.1-blue.svg)
A CI-friendly release automation tool for GitFlow workflows using Conventional Commits. A CI-friendly release automation tool for GitFlow workflows using Conventional Commits.