The GitHub Actions job "Tests" on airflow.git/move-helm-tests-to-chart has 
failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
c6b1749cd0d12ca912fdd50c5da6ccccb5ff7040 / Jarek Potiuk <[email protected]>
Tighten chart/.helmignore and verify packaged chart contents in CI

Locally building the chart with `breeze release-management
prepare-helm-chart-package` after the helm-tests → chart/tests move
revealed that the published chart `.tgz` was bundling four files that
chart consumers do not need and that we did not realise had been
shipping for a while:

* `pyproject.toml` (workspace-member metadata for the chart's pytest /
  mypy config — irrelevant to consumers)
* `.pre-commit-config.yaml` (local dev/CI hook config)
* `docs/` (chart documentation source — rendered to
  airflow.apache.org/docs/helm-chart/, not needed inside the .tgz)
* `newsfragments/` (towncrier source for building RELEASE_NOTES.rst at
  release time)

Add all four to `chart/.helmignore` so they are no longer bundled.

To make sure this doesn't drift again, add a small verification script
`scripts/ci/verify_helm_chart_package.py` that:

* Reads the packaged `.tgz` and asserts the top-level entries match an
  explicit allowlist (Chart.yaml, values.yaml, templates/, etc.). Any
  newly-introduced top-level file fails the check until it is either
  added to the allowlist (chart-relevant) or to `.helmignore` (dev-only).
* Runs `helm lint` against the same `.tgz`.

Wire the script into the existing `tests-helm-release` job in
`.github/workflows/helm-tests.yml`, right after
`prepare-helm-chart-package` produces the artifact and before signing,
so a regression in the packaged set fails CI immediately.

The script is also runnable locally:

    uv run scripts/ci/verify_helm_chart_package.py dist/airflow-1.22.0.tgz

Report URL: https://github.com/apache/airflow/actions/runs/25467164149

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to