You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Alexander Fedulov (Jira)" <ji...@apache.org> on 2025/02/20 12:26:00 UTC
[jira] [Updated] (FLINK-37360) Update japicmp configuration post 1.20.1
[ https://issues.apache.org/jira/browse/FLINK-37360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexander Fedulov updated FLINK-37360:
--------------------------------------
Affects Version/s: 1.20.1
(was: 1.20.2)
> Update japicmp configuration post 1.20.1
> ----------------------------------------
>
> Key: FLINK-37360
> URL: https://issues.apache.org/jira/browse/FLINK-37360
> Project: Flink
> Issue Type: Technical Debt
> Affects Versions: 1.20.1
> Reporter: Alexander Fedulov
> Assignee: Alexander Fedulov
> Priority: Major
>
> 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)