2.1 KiB
ConfigKit v0.4.2
This patch release simplifies and safeguards source publication and aligns maintainer policy and licensing guidance. Library behavior is unchanged.
Summary
Maintainers can now publish a prepared release with one guarded command. It
validates the exact committed candidate, checks the authoritative destination,
and pushes only the candidate on main and its annotated version tag. The
release procedure explains preparation and partial-publication
recovery; successful tag publication completes the source-only release without
waiting for CI or consumer retrieval.
Compatibility
No Go code, public API, configuration semantics, diagnostic behavior, or
dependencies changed from v0.4.1. The minimum Go version remains 1.25. Linux
amd64 and arm64 remain release-validated; macOS remains best-effort. The YAML
dependency remains go.yaml.in/yaml/v4 v4.0.0-rc.6.
Upgrade
Select this version and rebuild:
go get gitea.maximumdirect.net/eric/ConfigKit@v0.4.2
No application-code or configuration migration is required from v0.4.1.
Changes
- Add guarded single-command publication with exact candidate, version, and remote checks; note-derived annotated tags; and bounded failed-push recovery.
- Keep one offline race suite, one full vet pass, and Linux amd64/arm64 builds as release gates. Formatting and whitespace remain development checks; dependency tidiness is reviewed when dependencies change.
- Align adopted policies and contributor guidance with their pinned upstream revision, and include the CC BY-SA 4.0 license text and attribution for adapted policy material. The project grant remains LGPL-3.0-or-later.
- Retire completed release-workflow and policy-alignment planning records while preserving their history in Git. Deferred scope remains documented.