ci: run backend tests for provider bundle changes

[erichare]

Summary

Adds src/bundles/** to the python path filter in .github/changes-filter.yaml.

Why

.github/workflows/ci.yml gates the backend suite on the python filter:

  test-backend:
    if: |
      ...
        needs.path-filter.outputs.python == 'true')

That gate was added in #13614 (2026-06-15) to stop frontend-only PRs from paying for the backend suite. But the python filter still lists only src/backend/**, src/lfx/**, pyproject.toml and uv.lock — it never learned about src/bundles/** after the bundle metapackage split.

So a PR that only touches a provider bundle resolves python=false and skips the entire backend suite, including the bundle's own tests under src/bundles/*/tests/.

Before the gate landed, this was invisible: #13514 changed exactly two files — src/bundles/ibm/.../db2_vector.py and src/bundles/ibm/tests/test_db2_vector.py — and still ran all 17 backend jobs, because test-backend was then gated only on docs-only != 'true'. The same PR today would run none of them, and the test file it modified would never execute.

Bundle PRs that happen to touch uv.lock or pyproject.toml (most new bundles do) still match the filter, which is why this hasn't bitten yet — but any edit confined to an existing bundle's Python silently loses backend coverage.

Blast radius

path-filter.outputs.python has four consumers in ci.yml:

Line	Consumer	Effect
253	test-backend	now runs for bundle-only PRs — the fix
340	test-templates	now runs for bundle-only PRs — desirable; bundle components appear in starter templates
200	docs-only computation	only ever makes docs-only harder to be true; cannot mis-skip
493	CI Success echo	cosmetic

No effect on Playwright shard selection — that is driven by the separate suite filters (components, workspace, api, …), which are deliberately left alone here. See the note below.

Deliberately not changed

I also considered adding src/bundles/** to the components suite filter, but that would reduce coverage. When no suite matches, typescript_test.yml falls through to @release:

if [[ ${#TAGS[@]} -eq 0 ]]; then
  SUITES='["release"]'
  TAGS=("@release")

So bundle-only PRs already get the full @release suite (~411 tests, 70 shards — #13514 ran 64 shards under the smaller suite of the time). Mapping bundles to components would narrow that to @components (~73 tests, 16 shards). The frontend side is already behaving conservatively and is left as-is.

Two adjacent gaps, both out of scope here:

• docker filter also omits src/bundles/**, so bundle-only PRs skip test-docker even though bundles ship in the full image.
• scripts/check_changes_filter.py (the "Validate Filter Coverage" step) only inspects paths under src/frontend/, which is why no one was told about this. Widening it to src/bundles/ would catch the next instance.

Validation

• .github/changes-filter.yaml parses; python list contains src/bundles/**.
• Confirmed against the current ci.yml that all four outputs.python consumers behave as tabulated above.

Summary by CodeRabbit

• Chores
  • Updated change classification so modifications within Python bundles are correctly recognized as Python-related changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: c69d4748-b899-4682-a90e-af9202b5af80

📥 Commits

Reviewing files that changed from the base of the PR and between 48aac8b and 7fb2277.

📒 Files selected for processing (1)

• .github/changes-filter.yaml

Included review availability: Your plan includes up to 10 reviews per rolling hour; 8 remain after this review.

---

Walkthrough

The Python change-detection filter now includes changes under src/bundles/**.

Changes

Python change detection

Layer / File(s)	Summary
Include bundle paths .github/changes-filter.yaml	Adds src/bundles/** to the paths classified as Python changes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 7fb22

This localized CI filter change ensures backend checks run for provider bundle-only updates, with no actionable merge-blocking risk remaining beyond normal checks and review.

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 error, 1 warning)

Check name	Status	Explanation	Resolution
Test Coverage For New Implementations	❌ Error	The PR fixes a CI path-filter bug, but its only changed file is .github/changes-filter.yaml; no regression test verifies that bundle-only paths set python=true.	Add a focused regression test for the filter configuration that covers a src/bundles/** change and verifies backend-test selection.
Test Quality And Coverage	⚠️ Warning	The commit changes path-filter behavior but adds no regression test; the diff has one YAML file and zero test files, so bundle matching and backend triggering are not tested.	Add an automated CI/config test that parses the filter and verifies representative src/bundles files set python=true and satisfy the backend job condition.

✅ Passed checks (7 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the filter change that runs backend tests for provider bundle changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Test File Naming And Structure	✅ Passed	The PR changes only .github/changes-filter.yaml; it adds no test files or test code, so the naming and structure check has no introduced violation.
Excessive Mock Usage Warning	✅ Passed	The diff changes only .github/changes-filter.yaml; it adds no test files, mocks, stubs, or test behavior to review.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/bundles-python-path-filter

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

✅ Test Coverage Advisor

No source changes detected without accompanying tests. Thanks for keeping coverage up! 🎉

Advisory check only — never blocks merge.

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	53.1% (78256/147367)	70.92% (11081/15623)	48.74% (1830/3754)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
6138	0 💤	0 ❌	0 🔥	25m 21s ⏱️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.13%. Comparing base (51cd936) to head (7fb2277).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14605      +/-   ##
==========================================
- Coverage   64.96%   59.13%   -5.83%     
==========================================
  Files        2456     2419      -37     
  Lines      251004   241989    -9015     
  Branches    34940    17551   -17389     
==========================================
- Hits       163054   143103   -19951     
- Misses      85885    96821   +10936     
  Partials     2065     2065              

Flag	Coverage Δ
frontend	53.10% <ø> (-9.70%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 887 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.