You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "lincoln lee (Jira)" <ji...@apache.org> on 2024/03/18 06:26:00 UTC
[jira] [Created] (FLINK-34707) CLONE - Update japicmp configuration
lincoln lee created FLINK-34707:
-----------------------------------
Summary: CLONE - Update japicmp configuration
Key: FLINK-34707
URL: https://issues.apache.org/jira/browse/FLINK-34707
Project: Flink
Issue Type: Sub-task
Reporter: Sergey Nuyanzin
Assignee: Sergey Nuyanzin
Fix For: 1.19.0, 1.18.1
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)