To update to the latest beta release of Meteor 1.3.3, simply run
meteor update --release 1.3.3-beta.2
in any Meteor application directory. If you encounter problems, please either file issues on GitHub or ask questions on the GitHub tracking issue.
Meteor 1.4 will follow very shortly after Meteor 1.3.3, with newer versions of Node and MongoDB, and relaxed package version constraints, all of which are already implemented, tested, and merely waiting to be released. You might ask, then: why even release Meteor 1.3.3, instead of jumping directly to Meteor 1.4? A few reasons:
- Though Meteor 1.3.3 is a more conservative release than 1.4, it contains a number of noteworthy changes since 126.96.36.199, so we wanted to make sure users who aren’t ready for major updates to Node or Mongo can still get the improvements in 1.3.3.
- It will be much easier to distinguish between Meteor-specific bugs and bugs related to the Node/Mongo upgrades if we have a recent version of Meteor that includes everything except those upgrades.
- Updating to Meteor 1.3.3 before updating to Meteor 1.4 is a good way to make sure your app is fully up-to-date with the module system, testing, and Cordova changes introduced in 1.3, before you change another important variable in your stack.
Changes since Meteor 188.8.131.52.
Full announcement on GitHub.