[
https://issues.apache.org/jira/browse/FLINK-37361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17929188#comment-17929188
]
Alexander Fedulov commented on FLINK-37361:
-------------------------------------------
Merged into release-1.19:
https://github.com/apache/flink/commit/40250d3cb9cba346d880cc05f0d09f0fa585de11
> Update japicmp configuration post 1.19.2
> ----------------------------------------
>
> Key: FLINK-37361
> URL: https://issues.apache.org/jira/browse/FLINK-37361
> Project: Flink
> Issue Type: Technical Debt
> Affects Versions: 1.19.2
> Reporter: Alexander Fedulov
> Assignee: Alexander Fedulov
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.19.3
>
>
> 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)
