Jean-Luc Makiola a54a5d0220 fix(renovate): use a flexible internal-checks filter so ages resolve ...

Age came back `unknown` for every dependency, which is the previous
commit's `internalChecksFilter: none` doing exactly what it says on the
tin — and rather more. filter-checks.ts short-circuits on `none`:

    if (internalChecksFilter === 'none') {
      release = sortedReleases.pop();     // returns here
    } else {
      for (let candidateRelease of sortedReleases.reverse()) {
        ...
        const updatedCandidateRelease = await postprocessRelease(...)

postprocessRelease is the only caller that fetches a Maven artifact's
Last-Modified header, so skipping the loop leaves releaseTimestamp unset.
That empties the Age column, but it also silently voids minimumReleaseAge
and the stability status check, since both compare against that same
timestamp. The cooling-off tiers were decorative.

`flexible` keeps the intent — it still prefers a version that has cleared
its window, but opens the PR at the newest candidate when none has — while
running the loop that populates the timestamps. Verified with a local
dry-run: compose-bom 24 d, material3 1.5.0-alpha24 10 d, work-runtime
122 d, AGP 9.3.1 2 d, gradle 29 d. Only ghcr.io/renovatebot/renovate stays
unknown, because the docker registry serves no timestamps at all — the
run marks all 176 of its tags pending for that reason, and flexible is
what still lets that PR through.

Pending rejoins the table: under a flexible filter it names the newer
version being held back, rather than leaving it invisible.

Also migrates the Gitea workflow manager off the deprecated `fileMatch`.
Renovate's config migration was rewriting it to `managerFilePatterns`
(delimited regex) on every run and warning about it; the dry-run confirms
the manager still picks up .gitea/workflows afterwards.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-07-25 22:20:07 +02:00

5.1 KiB

Raw Blame History

View Raw