[
https://issues.apache.org/jira/browse/FLINK-32913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17786509#comment-17786509
]
Sergey Nuyanzin commented on FLINK-32913:
-----------------------------------------
Merged to master as
[5b8d7dfc7cfb31fcaa62cb5760e46047cab75fbd|https://github.com/apache/flink/commit/5b8d7dfc7cfb31fcaa62cb5760e46047cab75fbd]
> Update japicmp configuration
> ----------------------------
>
> Key: FLINK-32913
> URL: https://issues.apache.org/jira/browse/FLINK-32913
> Project: Flink
> Issue Type: Sub-task
> Reporter: Sergey Nuyanzin
> Assignee: Sergey Nuyanzin
> Priority: Major
> Labels: pull-request-available
>
> 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)
