There are a few things in here that could technically be considered "breaking changes" but only if the frontend has already integrate them, which in most cases I doubt. It includes stuff like:
Removing the return value from BelowMinRequiredVotingPower error. We can easily query the minimum required voting power from the contract, so this serves no purpose and introduces an inconsistency with some errors returning values and some not.
YieldDistributed event was changes to not return values that can be calculated easily on the frontend, given it has context of how the yield algorithm works. It helps to reduce the clutter in the distributeYield function significantly. @subject026 already confirmed this isn't used by the frontend.
Unused variables minHoldingDuration, minVotingAmount, & blockTime and related setter functions were removed.
There are a few things in here that could technically be considered "breaking changes" but only if the frontend has already integrate them, which in most cases I doubt. It includes stuff like:
BelowMinRequiredVotingPowererror. We can easily query the minimum required voting power from the contract, so this serves no purpose and introduces an inconsistency with some errors returning values and some not.resolveYieldDistributionwas changed to not revert, but return return "false" if the yield is not distributable as per thee Powerpool documentation (https://docs.powerpool.finance/powerpool-and-poweragent-network/power-agent/user-guides-and-instructions/i-want-to-automate-my-tasks/job-registration-guide#resolver-job). Related errors were removed.YieldDistributedevent was changes to not return values that can be calculated easily on the frontend, given it has context of how the yield algorithm works. It helps to reduce the clutter in thedistributeYieldfunction significantly. @subject026 already confirmed this isn't used by the frontend.minHoldingDuration,minVotingAmount, &blockTimeand related setter functions were removed.