rluvaton opened a new issue, #21406:
URL: https://github.com/apache/datafusion/issues/21406
### Is your feature request related to a problem or challenge?
I've just upgraded from datafusion 51 to 52 and now from 52 to 53, and in
both cases not all breaking changes were listed in the upgrade guide which
makes me dig the original change and understand it and what was before in order
to update
### Describe the solution you'd like
If we could have a GitHub action that track breaking changes (not behavior
ones) and mark them with a label as a start.
Since clippy already know if the function is really public or not (like
`pub(crate) mod a { pub mod b { } }` `mod b` is not really public we can use
that somehow to check whether a change that was made in each pr is a breaking
change regarding, and we can output a report of each breaking change in the pr,
(like removed function a, b. added to trait function c with no default
implementation, added argument to a function, changed visibility)
### Describe alternatives you've considered
Pain when I upgrade to encounter it myself
### Additional context
_No response_
--
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]
