Closed patrickgordon closed 5 years ago
This depends upon the version you were coming from. By any chance have you built dab manually or switched to the stable
branch/tag recently?
Yep switched to stable recently.
On Thu, 7 Mar 2019 at 12:35 pm, Nekroze notifications@github.com wrote:
This depends upon the version you were coming from. By any chance have you built dab manually or switched to the stable branch/tag recently?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Nekroze/dab/issues/363#issuecomment-470360197, or mute the thread https://github.com/notifications/unsubscribe-auth/ADCPwhLMzLvdmr4_Fldfsm43qVpRj9N1ks5vUHsCgaJpZM4bh47X .
Keep an eye out next time it updates as I have seen this work very recently, I think switching branches causes this behaviour. If it does not happen every time I think the outcome here might just be putting some (reasonable) limit on the changelog output to catch this and if you have not updated for say a year.
master has been updated a few times now, hows it looking for you @patrickgordon?
Hey @Nekroze yep looks like it was just from switching tags to stable. Only reports the diff now. Cheers
Happy to hear that. Thanks for the report.
Bug Report
Describe the bug
When the dab auto-update runs, it provides the full changelog instead of the diff.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Should only display the commits between current and latest version
Example
dab version
output