It’s been about a month since we first released Meteor 3.0, and we are proud to announce that a new patch is now available, increasing stability and reliability.
This patch mainly restores the correct behavior for subscriptions, where documents were first removed, then readded on parameter changes, and subscriptions were started before being fully authenticated. We also focused on updating our guides and docs, with more to come.
What changed in v3.0.2
Merge release-3.0 into devel and safe keep v2 branch
All documents still removed upon subscription update/addition
Review and update the migration guide
Make information about git cloning clearer in 3.0 CLI
Deprecate Meteor.user() in the server
Improve Meteor.applyAsync doc
Fix AppVeyor CI
Investigate accounts authentication issue with Meteor 3 (subscription related)
Investigate and optimize subscriptions being recreated after login call (fix for all subscriptions)
Review v3 docs and update old version references
Fix deprecation warnings when we install Meteor 3
Investigate setx issue and meteor install on Windows
How to test it?
Installing Meteor
npx meteor
Existing projects:
meteor update --release 3.0.2
Starting a project:
meteor create app-name --release 3.0.2
Your help testing this version by creating a new app or migrating your current one will be extremely helpful!
Please give us your feedback, and if you find any issues, you can create a post here or open an issue on GitHub .
WE DEM BOYZ! Loving the releases! I’ve already updated some big Meteor codebases to 3.0. I keep running meteor update and expecting these releases to be there though! I think it’s time to mainline 3.0 and make it the official recommended edition!!!
The releases are exciting, but I think it’s still early. In projects it’s usually not only meteor that is used. Meteor packages still don’t fully support 3.0 and we have to wait for them to migrate.
meteor update --release 3.0.2
=> Errors while initializing project:
While checking for email@3.0.1:
error: No compatible binary build found for this package. Contact the package author and ask them to publish it for your platform.
@pmogollon Worked like a charm, thanks. However, if I have no version constraint in my packages file, should meteor pickup the latest version for each package automatically if I do a meteor update?
What package is it coming from? There should not be any change in importing stuff from Atmosphere packages as far as I know (barring changes in the package itself).
Fully agree, I’m far away on all my projects from 3.x - mostly due to outdated and no longer maintained but yet almost core (eg Kadira packages) packages that many people surely have in their projects as well.
It’s a great start and keep those new versions coming but the focus should also be on the packages that need to be pushed to 3.x to get a lot more people version 3.x ready.
It’s surely not only about the required code changes going async in your code base (though that’s a big task for most still).
