The GitHub Actions job "prek" on 
airflow-steward.git/pr-management-stats-reference-impl-and-fixes has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
d293dc046c9a16bf65f9790da47469e57246e398 / Jarek Potiuk <[email protected]>
chore(ci): fix dependabot cooldown schema and bump pinned actions

The github-actions and pre-commit ecosystem blocks in
.github/dependabot.yml carried `semver-{major,minor,patch}-days`
cooldown keys, which those ecosystems do not accept. Dependabot
rejected both blocks outright with:

    The property '#/updates/0/cooldown/semver-major-days' is not
    supported for the package ecosystem 'github-actions'.
    The property '#/updates/1/cooldown/semver-major-days' is not
    supported for the package ecosystem 'pre-commit'.
    ...

which is why neither ecosystem produced a single PR in the four
weeks since adoption on 2026-04-29 (the uv blocks were unaffected
and ran normally — see #130, #233). Strip the unsupported keys and
keep `default-days: 7` for the 7-day settle window.

Apply the bumps that would have landed already had dependabot been
running, all past the 7-day cooldown:

  actions/cache                v4.2.2  -> v5.0.5
  github/codeql-action         v4.35.2 -> v4.35.5
  zizmorcore/zizmor-action     v0.5.2  -> v0.5.6
  astral-sh/setup-uv           v7.3.0  -> v8.1.0

actions/cache@v5 needs runner >= 2.327.1 (Node 24), which the
GitHub-hosted runners we target already satisfy. setup-uv@v8 is a
major bump; CI on this commit is the smoke test.

ASF allowlist: setup-uv@08807647 and zizmor-action@5f14fd08 are
already on approved_patterns.yml. actions/cache and
github/codeql-action are exempt — `actions` and `github` are in
TRUSTED_OWNERS in apache/infrastructure-actions/allowlist-check/
check_asf_allowlist.py.

Generated-by: Claude Code (Opus 4.7)

Report URL: https://github.com/apache/airflow-steward/actions/runs/26374596130

With regards,
GitHub Actions via GitBox


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

Reply via email to