aether/vociferate
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

feat: default to release-version file
Some checks failed
Action Validation / validate-released-binary (amd64, ./vociferate, X64) (push) Failing after 6s
Details
Action Validation / validate-released-binary (arm64, qemu-aarch64-static ./vociferate, ARM64) (push) Failing after 23s
Details
Push Validation / validate (push) Successful in 52s
Details

Browse Source
This commit is contained in:
Micheal Wilkinson
2026-03-20 19:32:49 +00:00
parent a413385c4e
commit 2646d42523
7 changed files with 21 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@@ -44,10 +44,12 @@ go run ./cmd/vociferate --recommend --root .
Defaults:
- `version-file`: `internal/vociferate/version/version.go`
- `version-pattern`: `const String = "([^"]+)"`
- `version-file`: `release-version`
- `version-pattern`: `^\s*([^\r\n]+)\s*$`
- `changelog`: `changelog.md`
By default, `vociferate` reads and writes the release version as the sole content of a root-level `release-version` file. Repositories that keep the version inside source code should pass explicit `version-file` and `version-pattern` values.
## Testing
```bash
@@ -81,6 +83,7 @@ Use the composite action directly:
Set `version` only when you want to override the recommended version.
Pin the composite action to a released tag. It downloads a prebuilt Linux binary from vociferate releases and caches it on the runner, so it does not require installing Go.
If your repository uses the default plain-text `release-version` file, you can omit `version-file` and `version-pattern` entirely.
Call the reusable release workflow: