kosiew commented on issue #22192:
URL: https://github.com/apache/datafusion/issues/22192#issuecomment-4465506171
@rluvaton,
In #22196, the base-branch reason is preserved here: `check-semver-advisory`
still compares against `apache/${{ github.base_ref }}` and is reported
separately as advisory, so it remains the signal for API breakage introduced by
the PR itself.
The new latest-release check is intentionally a different signal: it answers
whether changed published crates remain compatible with the latest stable
release users can depend on. That is why the comment and label handling
distinguish “base branch compatibility — advisory” from “latest release
compatibility — blocking,” and the `auto detected api change` label is only
tied to the latest-release result.
On backports: this workflow currently only runs for PRs targeting `main`
(`pull_request.branches: [main]`), so this change does not affect `branch-*`
backport PRs as written.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
