top | item 5153858

(no title)

scotje | 13 years ago

Aha, well apparently I never merged that commit into my deploy branch, so it was still actually on 3.2.1. That combined with the fact that your page had said 3.2.1 was safe caused my brain to short circuit and not realize that 3.2.11 is what it needed to be on. :) I'll redeploy and check it again, thanks guys!

discuss

order

borski|13 years ago

Yeah, that was totally our bad. I'm deploying the typo fix now.

Let me know if you have any other issues! Happy to help.

scotje|13 years ago

See, in a very circular way I was just reporting the typo. :)

(Looks good now that I have the right release deployed, by the way.)