feat(release): publish OTP tarball + GHCR image on semver tag - #12
Merged
Merged
Conversation
Add .github/workflows/release.yml triggered on `v*` tags. Two parallel jobs: `mix release` tarball attached to a GitHub Release, and a container image pushed to ghcr.io/liquidmetal-dev/brigade. Version is driven by the git tag (v-stripped) via BRIGADE_VERSION. Supporting changes: - mix.exs: releases: block (assemble+tar) + env-driven version - config/runtime.exs: prod env-driven runtime config - Dockerfile + .dockerignore: multi-stage prod release image - drop google_protos dep: protobuf ~> 0.14 bundles the same Google.Protobuf.* modules; duplicates fail `mix release` assembly - README: Releases section
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.
What
New
.github/workflows/release.ymltriggered on semver tag push (v*). Builds a release and publishes two artifacts to GitHub:mix releaseoutput (bundles ERTS) attached to a GitHub Release viasoftprops/action-gh-release@v2.-rc/-betatags marked prerelease.ghcr.io/liquidmetal-dev/brigade:<ver>(+:X.Y, and:latestfor stable tags).Version is driven by the git tag (
vstripped) viaBRIGADE_VERSION;mix.exskeeps a dev fallback. No manual bump at release time.Supporting changes
mix.exs—releases:block (:assemble, :tar) +version: System.get_env("BRIGADE_VERSION") || "0.1.0"config/runtime.exs— prod env-driven runtime config (BRIGADE_GRPC_PORT,BRIGADE_AUTH_TOKEN,FLINTLOCK_ENDPOINT, …); guarded to:prod, unset vars fall back toconfig/config.exsDockerfile+.dockerignore— multi-stage prod image (build onhexpm/elixir:1.18.4-erlang-27.3.4.14-..., runtimedebian:bookworm-slim, non-root)google_protosdep —protobuf ~> 0.14bundles the sameGoogle.Protobuf.*modules; duplicate modules failmix releaseassembly (dev/test only warned)README.md— Releases sectionVerification (local)
MIX_ENV=prod BRIGADE_VERSION=0.0.0-test mix release→ tarball emitted,bin/brigade version→brigade 0.0.0-testdocker build→docker run brigade:test version→brigade 0.0.0-testmix format --check-formatted,mix compile --warnings-as-errors,mix test(27 tests, 0 failures) all passTag-triggered run itself is untested (needs a pushed tag) — suggest a dry-run on a
v0.0.0-rc1tag before the first real release.🤖 Generated with Claude Code