Its actually by design. I guess the update message should read something like.. last update changes (but you may have other changes)
What happens is the script pack has a CRC32 hash and description of the change from github that is saved to the update check. Then Bit Che checks if this CRC32 is different than the last fetched download stored on the PC and displays the notice plus the description of the last update. If you proceed with the update, the full new script pack is downloaded and then Bit Che itself performs the reconciliation of what has changed.
So, there actually isn't an easy way to improve this without a whole new update design which would have to increase server precessing and/or bandwidth. One idea would be to show the changes after the script pack is downloaded but before its applied but then again, the first update Details message would only show the last github change.
Thoughts?