Skip to content

Modernize and migrate builder workflow to new builder actions#130

Merged
frenck merged 4 commits intomainfrom
migrate-builder-actions
Mar 24, 2026
Merged

Modernize and migrate builder workflow to new builder actions#130
frenck merged 4 commits intomainfrom
migrate-builder-actions

Conversation

@sairon
Copy link
Member

@sairon sairon commented Mar 24, 2026

Replace the monolithic builder container with the new builder GitHub Actions. Split the workflow into a main orchestrator (builder.yaml) that detects changed apps, and a reusable per-app workflow (build-app.yaml) that handles single app build.

Also, replace unmaintained jitterbit/get-changed-files with tj-actions/changed-files.

Closes home-assistant/epics#35

Replace the monolithic builder container with the new builder GitHub
Actions. Split the workflow into a main orchestrator (`builder.yaml`)
that detects changed apps, and a reusable per-app workflow
(`build-app.yaml`) that handles single app build.

Also, replace unmaintained `jitterbit/get-changed-files` with
`tj-actions/changed-files`.

Closes home-assistant/epics#35
Copy link
Member

@frenck frenck left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, @sairon 👍

../Frenck

                       

Blogging my personal ramblings at frenck.dev

@frenck frenck merged commit b09b6e5 into main Mar 24, 2026
8 checks passed
@frenck frenck deleted the migrate-builder-actions branch March 24, 2026 17:40
*) echo "Unsupported TARGETARCH: ${TARGETARCH}" && exit 1 ;; \
esac \
&& curl -sSLf -o /usr/bin/tempio \
"https://github.com/home-assistant/tempio/releases/download/${TEMPIO_VERSION}/tempio_${tempio_arch}"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, not really new, but tempio is actually in the base image, so this is somewhat a bad example 🤔 😅

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, right 😅 It does no harm as it works and just displays some patterns but we can come up with something more practical.

COPY rootfs /

LABEL \
io.hass.type="addon" \
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we maybe introduce app?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC Supervisor doesn't really consume it but defines it amongst its consts. So we should at least add it there (and maybe make some use of it?). Let's do it in a follow-up there and here before we update the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

addons-example: migrate example add-on build away from legacy builder action

3 participants