chore: release v0.4.0#46
Open
mkappworks wants to merge 1 commit into
Open
Conversation
mkappworks
force-pushed
the
release-please--branches--main--components--cloudzilla-app
branch
from
24fa264 to
794e679
Compare
mkappworks
force-pushed
the
release-please--branches--main--components--cloudzilla-app
branch
from
794e679 to
50f6c48
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release ready for review
0.4.0 (2026-05-22)
Features
Bug Fixes
build-and-publish.yml(chained fromrelease-please.yml) to build multi-arch Go binaries (linux/darwin × amd64/arm64), package tarballs with SHA256 sums, push a multi-arch Docker image to GHCR, and attach assets to the draft release. The git tag is created up front (force-tag-creation: true) so the chained build has a stable anchor before the release is published.CHANGELOG.mdmanually — release-please owns it. The version itself is injected into the binary at build time via-ldflags="-X main.version=${TAG}", so there is no version file to hand-edit.