You're welcome for the work, thanks for letting me know about the glitch!

UPDATE: I've changed the master branch so that it can't be changed unless a PR is created. I frequently would update docs on master in between releases because I'm lazy. That laziness is what allowed that cherry-pick to get through :)

It's not quite just cosmetic, but the 1.41 branch doesn't have any change (other than version) in the installer, so you're good. I must have just cherry picked something I didn't mean by accident when I was touching up documentation after releasing 1.40.

I'm mistaken, you have uncovered a bug. I have a release script that bumps that version number on release. In the last couple of releases, I moved that code to a library so I could test building the installer outside of the release functionality. In this case, it shouldn't increase the version number to what the current branch is. In any case, it bumped the version, but I also did cherry pick a file I shouldn't have.

I'll add a fix to the current branch, and I'll just release 1.41 today instead of reversing the accidental change.

Thanks,

-stevieb