Skip to content

ci: run workflows on the v4 branch, not just master#3013

Merged
vishr merged 1 commit into
v4from
ci/run-on-v4-branch
Jun 14, 2026
Merged

ci: run workflows on the v4 branch, not just master#3013
vishr merged 1 commit into
v4from
ci/run-on-v4-branch

Conversation

@vishr

@vishr vishr commented Jun 14, 2026

Copy link
Copy Markdown
Member

Problem

The v4 LTS maintenance branch receives no CI. Both echo.yml (Run Tests) and checks.yml (Run checks) trigger only on master — a stale snapshot from when v4 was the default branch. As a result, PRs targeting v4 (e.g. the recent security backport #3011) get zero automated testing and must be dispatched manually.

Fix

Add v4 to the push and pull_request branch filters in both workflows.

Note on this PR

Because pull_request workflows run from the base branch's config, this PR itself won't auto-run CI (the base v4 doesn't have the trigger yet — chicken-and-egg). I've dispatched both workflows manually on this branch to validate the YAML and confirm they pass. After merge, all future v4 pushes/PRs will be tested automatically.

🤖 Generated with Claude Code

The v4 LTS maintenance branch received no CI because both workflows triggered
only on master (a stale snapshot from when v4 was the default branch). Add v4 to
the push and pull_request branch filters so v4 PRs and pushes are tested.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@vishr vishr merged commit aa52f6a into v4 Jun 14, 2026
14 of 16 checks passed
@vishr vishr deleted the ci/run-on-v4-branch branch June 14, 2026 16:31
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