Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 1.9.3 #10961

Merged
merged 4 commits into from
Mar 10, 2020
Merged

Release 1.9.3 #10961

merged 4 commits into from
Mar 10, 2020

Conversation

filipenevola
Copy link
Collaborator

We have a few users having complicated issues with MongoDB Driver version 3.2.7 so we are doing this release just to upgrade MongoDB Driver to 3.5.4.

@cfnelson
Copy link
Contributor

cfnelson commented Mar 7, 2020

Our Web App (Meteor v1.9.2, running on Meteor Galaxy) had been running for a few days without any code changes.

Unexpectedly we started to receive errors for login and -> MongoTimeoutError: Server selection timed out after 10000 ms for every query. This disabled anyone being about to login or remain connected to our Web App.

Updating from Meteor 1.9.2 to -> 1.9.3.rc.0 meteor update --release 1.9.3-rc.0 and redeploying resolved the issue for us. Will monitor to confirm that it handles a re-connect failover.

Many thanks 🎉 🙇

@filipenevola filipenevola merged commit b7a8b1e into master Mar 10, 2020
@filipenevola filipenevola deleted the mongodb-fix-driver branch March 10, 2020 02:44
@filipenevola
Copy link
Collaborator Author

Meteor 1.9.3 is published!

@acemtp
Copy link
Contributor

acemtp commented Mar 12, 2020

Are you sure it's published?

doing a "meteor update" returns:

$ app git:(master) meteor update
This project is already at Meteor 1.9.2, the latest release.

@jnurkka
Copy link

jnurkka commented Mar 12, 2020

Are you sure it's published?

doing a "meteor update" returns:

$ app git:(master) meteor update
This project is already at Meteor 1.9.2, the latest release.

Do meteor update --release 1.9.3, that should work. Maybe your meteor CLI doesn't know of the newest release yet.

@hexsprite
Copy link
Contributor

Just because a new update is published doesn't mean it's "recommended" yet. So meteor update won't automatically update, but explicitly choosing the version will. eg. meteor update --release 1.9.3. It might be good to change the message to indicate that it's the newest recommended version and that there may be newer versions published ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants