You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Zakelly Lan (Jira)" <ji...@apache.org> on 2025/11/10 08:18:00 UTC

[jira] [Created] (FLINK-38671) Update japicmp configuration post 2.0.1

Zakelly Lan created FLINK-38671:
-----------------------------------

             Summary: Update japicmp configuration post 2.0.1
                 Key: FLINK-38671
                 URL: https://issues.apache.org/jira/browse/FLINK-38671
             Project: Flink
          Issue Type: Bug
    Affects Versions: 2.0.1
            Reporter: Zakelly Lan
            Assignee: Zakelly Lan


Update the japicmp reference version and wipe exclusions / enable API compatibility checks for @PublicEvolving APIs on the corresponding SNAPSHOT branch with the update_japicmp_configuration.sh script (see below).

For a new major release (x.y.0), run the same command also on the master branch for updating the japicmp reference version and removing out-dated exclusions in the japicmp configuration.

Make sure that all Maven artifacts are already pushed to Maven Central. Otherwise, there's a risk that CI fails due to missing reference artifacts.

{code:bash}
tools $ NEW_VERSION=$RELEASE_VERSION releasing/update_japicmp_configuration.sh
tools $ cd ..
$ git add *
$ git commit -m "Update japicmp configuration for $RELEASE_VERSION"
{code}





--
This message was sent by Atlassian Jira
(v8.20.10#820010)