Ahhh, makes sense.

You are correct, in that thinking back the version number did update correctly the first time I ran the update, but after having my initial problem I ran through all of the update steps manually to make sure that I didn't miss any sql updates, and in so doing reverted the version number that way. I didn't actually run the entire update script again, which is why the version number didn't get updated to the correct number again.