ci: trigger CI on release/* branches#661
Conversation
The release/v0.9.x branch was not covered by CI because the branch pattern 'v[0-9].[0-9]+.x' doesn't match the 'release/' prefix. PRs targeting release branches were merged without lint, compile, or test checks, which allowed broken cherry-picks to slip through (see the v0.9.19-beta tagged release failure). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Greptile SummaryThis PR fixes a gap in the CI workflow where branch filters ( Key changes:
Issue found:
Confidence Score: 4/5
Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
trigger["push / pull_request\nmain | v[0-9].[0-9]+.x | release/**"]
vw[validate-wrapper]
lint[lint]
ta[threading-audit]
pg[proguard-verification]
pt[python-tests]
kt[kotlin-tests]
it[instrumented-tests]
gate["ci-passed ✅"]
trigger --> vw
trigger --> lint
trigger --> ta
lint --> pg
vw --> pg
lint --> pt
vw --> pt
lint --> kt
vw --> kt
lint --> it
vw --> it
vw --> gate
lint --> gate
ta --> gate
pg --> gate
pt --> gate
kt --> gate
it -. "result NOT checked\n⚠️ silent failure" .-> gate
|
Summary
v[0-9].[0-9]+.x) didn't matchrelease/v0.9.x— therelease/prefix was missing from the pattern'release/**'to bothpushandpull_requesttriggersTest plan
🤖 Generated with Claude Code