git? this is a mercurial repo.
perhaps a commit was made that you forgot about. you can hg out before running astyle to check.
I went to Commit [0f2c3e] Summary and scrolled down and saw cprint.c changed.
I believe the consensus for astyle changes is that their commit is just for style changes, not other changes. Specifically run astyle then commit. Style changes that happen to come in from editor preference when making other changes are ok. I mention this because I checked your commit and saw other content changes that weren't just styling.
So, no diffs then from running astyle. Branch and ticket can be closed. Everyone should use 3.6.13 and wiki's (if any which address this) updated. Ken
I built astyle version 3.6.12 on my linux box and use it. I wasn't aware we had to use a specific version of it. Personally, I'm for keeping more up to date styling despite what's available as a package. If windows, mac, linux have a 3.6.x, we ought to use it to be consistent. I also came up with the .editorconfig to hopefully match what it puts out, so there's less style changes. I also use nvim, and noticed way too late that style changes were being automatically performed which is why I came up...
Flatpak
Flatpak