Skip to content

Tracking: weekly, grouped Dependabot updates and release-time license version checks #20732

Description

@amaechler

Motivation

Dependabot opens one PR per artifact every day. Over the 13 weeks to 2026-10-22 that was 381 of 696 commits on master and about 18% of PR runs of the unit-test workflow, and 166 of those PRs needed a manual licenses.yaml edit before they could pass. The dev@ discussion is here: https://lists.apache.org/thread/7y1bkvbb6og394mph4lx2x35dktv38nk

This issue tracks the individual PRs. Each item can be picked up on its own unless it says otherwise.

Dependabot configuration

licenses.yaml: check versions at release time instead of on every PR

Related: #20707 (merged) makes the license check cover the modules the release LICENSE includes, #20737 (merged) corrects per-module versions that had drifted from what the release ships, and #20764 (merged) reads licenses.yaml versions as strings and fails on unknown license names.

Related CI cleanups

Not part of the proposal, but they also reduce CI load or are needed for the ASF GitHub Actions policy.

Activity

  1. self-assigned this
    on Oct 26, 2026
  2. added theissue type on Oct 26, 2026
  3. amaechler commented on Oct 28, 2026

    @amaechler
    ContributorAuthor

    Reopening: GitHub closed this automatically when #20736 merged, but the check-licenses.py warn mode and the release guide step are still open.

  4. FrankChen021 commented on Oct 28, 2026

    @FrankChen021
    Member

    #20765 (comment)

    Based on the PR 20765 raised after the grouping, I think we should DISABLE upgrading these dependencies by bot:

    • org.codehaus.mojo:javacc-maven-plugin
    • check-style
    • spotbugs

    These should be upgraded manually

  5. amaechler commented on Oct 28, 2026

    @amaechler
    ContributorAuthor

    Thanks for flagging this. Instead of turning them off completely, #20776 takes javacc-maven-plugin, checkstyle and spotbugs-maven-plugin out of the weekly group, so each of their updates gets its own PR that can be fixed or closed without holding up the rest. That keeps new releases visible. If they're still too noisy, we can switch to ignore rules.

  6. pinned this issue on Oct 29, 2026
  7. unpinned this issue on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions