Skip to content

fix: snapshot job skips chrome publish on push triggers#9

Merged
ryanbas21 merged 1 commit into
mainfrom
fix/snapshot-chrome-publish
May 10, 2026
Merged

fix: snapshot job skips chrome publish on push triggers#9
ryanbas21 merged 1 commit into
mainfrom
fix/snapshot-chrome-publish

Conversation

@ryanbas21
Copy link
Copy Markdown
Owner

@ryanbas21 ryanbas21 commented May 10, 2026

Summary

  • Both snapshot and release jobs were running on every trigger (push and workflow_dispatch) because neither had a job-level if: condition
  • Added if: github.event_name == 'workflow_dispatch' to the snapshot job so it only runs on manual dispatch
  • Added if: github.event_name == 'push' to the release job so it only runs on merge to main
  • Reverted inputs.extension condition back to simple form since snapshot is now guaranteed to be workflow_dispatch-only

Test plan

  • Push to main triggers only the release job (changesets), not snapshot
  • Manual workflow_dispatch triggers only the snapshot job, not release
  • Manual dispatch with extension: true (default) publishes the Chrome extension to testers
  • Manual dispatch with extension: false skips the Chrome extension steps

🤖 Generated with Claude Code

inputs.extension is null when triggered by push (not workflow_dispatch),
causing the extension zip and publish steps to be silently skipped.
Use != false so the steps run by default and can still be opted out on
manual dispatch.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@ryanbas21 ryanbas21 merged commit 4e920e5 into main May 10, 2026
1 check passed
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