-
ReleaseKit v0.9.0 Stable
released this
2026-11-04 02:05:45 +00:00 | 0 commits to main since this releaseReleaseKit v0.9.0
ReleaseKit's maintained launchers and generated Go recovery commands now
prepare and run the release tool for the Go host when inheritedGOOSand
GOARCHselect another target. Release profiles still select the targets for
application builds.Launcher, delivery, and recovery fixes
- Local launchers and Woodpecker templates select the host before preparing
tool dependencies or compiling the CLI. Module-based launchers invoke
ReleaseKit by its full Go package path, so another registered tool named
releasekitdoes not make the invocation ambiguous. - Generated Go recovery commands select the host when run in a POSIX shell
and find the Go executable throughPATH. Recovery for API-only consumers
preserves both wildcard and version-specific module replacements when
relocating relative paths, fixing a panic after a failed publication. - The manual hosted-page retry stops if fetching or checking out the tag fails,
or if local edits remain. It checks the tagged checkout before downloading
dependencies or building the CLI.
Compatibility and upgrade
The module path remains
go.maximumdirect.net/releasekitand the Go consumer
minimum remains 1.26.0. Public Go APIs, release profiles, and publication
record formats are unchanged.Update copied launchers and CI templates to get the host and tool selection
fixes. Updating the module dependency alone does not update those files.
Configured product checks inherit the launcher's host target; if a check
needs an application target, set it explicitly in the check'senvmap
or command.See the adoption guide,
delivery guide,
and maintainer runbook
for updated recipes.Downloads
- Local launchers and Woodpecker templates select the host before preparing