What happened?
When accepting breaks, gradle-revapi uses the previous local tag when adding the lock-file entry (ref). However e.g. when devs work on a PR for a longer time, their local git tags might become out-of-date and the tag added to the lock-file is no longer the most recent tag.
Note that as a workaround, devs can refresh the tags manually (e.g. using git pull --tags).
What did you want to happen?
We might want to refresh the local git tags before evaluating the tag to be put into the lockfile to make sure that this is an up-to-date version.
What happened?
When accepting breaks, gradle-revapi uses the previous local tag when adding the lock-file entry (ref). However e.g. when devs work on a PR for a longer time, their local git tags might become out-of-date and the tag added to the lock-file is no longer the most recent tag.
Note that as a workaround, devs can refresh the tags manually (e.g. using
git pull --tags).What did you want to happen?
We might want to refresh the local git tags before evaluating the tag to be put into the lockfile to make sure that this is an up-to-date version.