Skip to content

fix(ci): start the publish workflows when release-tag pushes the tag - #57

Merged
easel merged 1 commit into
mainfrom
fix/release-tag-dispatch
Oct 2, 2026
Merged

easel merged 1 commit into
mainfrom
fix/release-tag-dispatch

Conversation

@easel

@easel easel commented Oct 2, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • A tag pushed with the default GITHUB_TOKEN does not trigger on: push: tags workflows, so the v0.14.1 tag created by release-tag.yml published no bundles, ran no install smoke, and deployed no tagged site.
  • release-tag.yml now dispatches release-genie-bundle.yml, install-smoke.yml, and pages.yml on the new tag (actions: write).
  • release-genie-bundle.yml gains a workflow_dispatch trigger.
  • The PR title is passed to the tag step through the environment instead of being interpolated into the shell.

This was the second commit on #55 and missed its merge.

🤖 Generated with Claude Code

A tag pushed with the default GITHUB_TOKEN does not trigger `on: push:
tags` workflows, so a tag created by release-tag.yml would publish no
bundles, run no install smoke, and deploy no tagged site. Dispatch
release-genie-bundle, install-smoke, and pages on the new tag after the
push, add the missing workflow_dispatch trigger to release-genie-bundle,
and pass the PR title to the tag step through the environment.

Co-authored-by: Erik LaBianca <erik.labianca@synaptiq.ai>
Co-Authored-By: Claude <noreply@anthropic.com>
@easel
easel merged commit 9c3f1a2 into main Oct 2, 2026
2 checks passed
@easel
easel deleted the fix/release-tag-dispatch branch October 2, 2026 01:25
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