Ta - that’s working. 
Well, actually, it LOOKED like it was working, however issuing meteor --version still reports 1.3.1
Not a silly question at all! We unrecommended 1.3.2.2 yesterday because we realized it contained a breaking change/improvement to DDP that wasn’t intended to be released until 1.3.3. Specifically, at least one package that relied on private methods of the DDP client Connection was broken in 1.3.2.1 and 1.3.2.2.
Though you can still manually meteor update --release 1.3.2.2 with no problem, and you may even notice some nice performance improvements due to DDP update batching, we’ve unrecommended it until we can publish a 1.3.2.3 (soon) without those changes.
Sorry for the confusion!
2 Likes
Thanks benjamn, however what about the fact that even when I manually specify the version (1.3.2.2), meteor --version still reports 1.3.1 - is that a bug?
Last time I tried to upgrade (to 1.3.1 from 1.3) the Meteor puked errors about npm peer dependencies, so shoud i bother even attempting to upgrade to this?