# Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). A `### Breaking` section is used in addition to Keep a Changelog's standard sections to explicitly document changes that are backwards-incompatible but would otherwise appear under `### Changed`. Entries under `### Breaking` trigger a major version bump in automated release recommendation logic. ## [Unreleased] ### Changed - The composite action now downloads and caches a released Linux `vociferate` binary instead of installing Go and running the module source directly. - Added workflow coverage for the released Linux binaries consumed by the composite action on both `amd64` and `arm64`. - Release preparation now runs directly in the release workflow; the repository-local helper script and just recipe were removed. - Release artifacts are now limited to `linux/amd64` and `linux/arm64` binaries plus `checksums.txt`. - The CLI entrypoint, internal package paths, build outputs, and automation references now use the `vociferate` name instead of the earlier `releaseprep` naming. - The release workflow and composite action now treat a provided `version` as an override and otherwise fall back to the recommended next version automatically. - Release creation is now idempotent: existing releases for the same tag are updated in place instead of recreated. - Release asset uploads now replace existing assets with matching filenames so reruns stay synchronized. - Release recommendation now forces a major version bump whenever a `### Breaking` heading is present in `## [Unreleased]`, even if the section has no bullet entries yet. - Reusable `workflow_call` support for the `Prepare Release` workflow, enabling other repositories to invoke it directly. - Automated release artifact publishing in the release workflow for `darwin`, `linux`, and `windows` binaries plus `checksums.txt`. - README guidance for release artifacts and examples for reusing vociferate as a composite action or reusable workflow. - Initial standalone vociferate migration from its earlier internal naming. - Configurable version source and parser via `--version-file` and `--version-pattern`. - Configurable changelog path via `--changelog`. - Composite action (`action.yml`) for release preparation and recommendation flows. - Gitea workflows for push validation and manual release preparation.