Skip to content

jenkinsci/plugin-pom updates not being offered due to incorrect Maven version logic #14102

@jglick

Description

@jglick

Is there an existing issue for this?

  • I have searched the existing issues

Package ecosystem

Maven

What you expected to see, versus what you actually saw

Splitting this out of #11068 (comment) for visibility since it appears to remain broken. For example https://github.com/jenkinsci/workflow-api-plugin/actions/runs/21574695951/job/62159764474 run on 2026-02-01 claims

No update needed for org.jenkins-ci.plugins:plugin 6.2108.v08c2b_01b_cf4d

which is wrong since that dep had at that time a newer version: https://github.com/jenkinsci/plugin-pom/releases/tag/6.2122.v70b_7b_f659d72

Example impact: jenkinsci/workflow-api-plugin#456 remains (as of this writing) the last update to this dep, which is bad since that included a bad change jenkinsci/plugin-pom#1286 that was subsequently reverted, but we cannot use DB to pick up the fix automatically.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions