Skip to content

validation of versions is not working as expected anymore #12711

@rnveach

Description

@rnveach

Identified at #12710 (comment) ,

./.ci/validation.sh versions needs to be updated.

Format of XML output files from internal command changed, and the script file no longer reports new versions.

The XML file use to contain <nextVersion> but target/dependency-updates-report.xml has the new example format:

    <dependency>
      <groupId>com.tngtech.archunit</groupId>
      <artifactId>archunit-junit5</artifactId>
      <scope>test</scope>
      <type>jar</type>
      <currentVersion>1.0.0</currentVersion>
      <lastVersion>1.0.1</lastVersion>
      <incrementals>
        <incremental>1.0.1</incremental>
      </incrementals>
      <status>incremental available</status>
    </dependency>
    <dependency>
      <groupId>org.junit-pioneer</groupId>
      <artifactId>junit-pioneer</artifactId>
      <scope>test</scope>
      <type>jar</type>
      <currentVersion>1.7.1</currentVersion>
      <lastVersion>2.0.0</lastVersion>
      <incrementals>
        <incremental>1.7.2</incremental>
      </incrementals>
      <minors>
        <minor>1.8.0</minor>
        <minor>1.9.0</minor>
        <minor>1.9.1</minor>
      </minors>
      <majors>
        <major>2.0.0</major>
      </majors>
      <status>incremental available</status>
    </dependency>

It is unclear if target/plugin-updates-report.xml has similar changes as the version I ran reported no updated.

The specifics of the new format will have to be confirmed with this update to ensure we can catch everything correctly.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions