Skip to content

ci: trigger release-asset build on release.published#2034

Merged
chubes4 merged 1 commit into
mainfrom
fix-release-asset-trigger
May 16, 2026
Merged

ci: trigger release-asset build on release.published#2034
chubes4 merged 1 commit into
mainfrom
fix-release-asset-trigger

Conversation

@chubes4
Copy link
Copy Markdown
Member

@chubes4 chubes4 commented May 16, 2026

Problem

#2031 added a build-release-asset job to .github/workflows/homeboy.yml gated on needs.homeboy.outputs.released == 'true'. v0.116.0 was released after that PR merged. The job was skipped on every release run and the ZIP never published.

Root cause: the reusable workflow at Extra-Chill/homeboy-action/.github/workflows/ci.yml@v2 only exposes a matrix output, not released / release-tag / release-version. Those outputs exist on homeboy-action's standalone release.yml workflow, but consumers calling the ci.yml reusable workflow don't get them. The gate needs.homeboy.outputs.released == 'true' was always evaluating to false.

Fix

Moves the asset build into its own .github/workflows/release-asset.yml file triggered on the release.published event. The release tag flows through github.event.release.tag_name — no dependency on the CI workflow's outputs.

Also exposes a workflow_dispatch input so an existing tag can be backfilled by hand.

Validation

  • YAML parse-checked both workflow files.
  • gh release upload --clobber semantics preserved.

Backfill

After merge, run the new workflow against v0.116.0:

gh workflow run release-asset.yml --ref main --field tag=v0.116.0

That will produce data-machine.zip on the existing v0.116.0 release without needing a new tag.

Related

AI assistance

  • AI assistance: Yes
  • Tool(s): Claude Code (Sonnet 4.5)
  • Used for: Inspected post-merge runs to find that build-release-asset was skipping silently, traced homeboy-action's ci.yml output set, identified the gate mismatch, and split the asset job into its own release-triggered workflow.

The homeboy.yml build-release-asset job gated on
needs.homeboy.outputs.released == 'true', but the
homeboy-action ci.yml reusable workflow only exposes a
'matrix' output, not 'released' or 'release-tag'. The
gate evaluated to false on every release run and the
ZIP never published.

This moves the asset build to its own workflow file
that fires on the release.published event. The release
event tag flows through github.event.release.tag_name
without depending on the CI workflow's outputs.

Also adds a workflow_dispatch input so an existing
release tag can be (re)built and uploaded by hand —
useful for backfilling v0.116.0 which released after
the previous PR landed but never got a ZIP.
@homeboy-ci
Copy link
Copy Markdown
Contributor

homeboy-ci Bot commented May 16, 2026

Homeboy Results — data-machine

Lint

lint — passed

Deep dive: homeboy lint data-machine --changed-since 8d58344

Test

test — passed

ℹ️ No impacted tests found for --changed-since 8d58344
ℹ️ Run full suite if needed: homeboy test data-machine
Deep dive: homeboy test data-machine --changed-since 8d58344

Audit

audit — passed

Deep dive: homeboy audit data-machine --changed-since 8d58344

Tooling versions
  • Homeboy CLI: homeboy 0.182.0+e9b9e964
  • Extension: wordpress from https://github.com/Extra-Chill/homeboy-extensions
  • Extension revision: 77a1b88
  • Action: unknown@unknown

@chubes4 chubes4 merged commit 64f38f1 into main May 16, 2026
5 checks passed
@chubes4 chubes4 deleted the fix-release-asset-trigger branch May 16, 2026 13:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant