Add mention of db fix when jumping back to older versions

This commit is contained in:
Hugh Willson
2018-03-01 07:49:19 -05:00
committed by Jesse Rosenberger
parent 9db6a437bc
commit 57ef6e9cc4

View File

@@ -67,6 +67,26 @@
`selftest.skip.define('some test', ...` will skip running "some test".
[PR #9579](https://github.com/meteor/meteor/pull/9579)
* Mongo has been upgraded to version 3.6.2 for 64-bit OS', and 3.2.18 for
32-bit OS'.
[PR #9632](https://github.com/meteor/meteor/pull/9632)
**NOTE:** After upgrading an application to use Mongo 3.6.2, it has been
noticed ([#9591](https://github.com/meteor/meteor/issues/9591))
that attempting to run that application with an older version of
Meteor (via `meteor --release X`), that uses an older version of Mongo, can
prevent the application from starting. This can be fixed by either
running `meteor reset`, or by repairing the Mongo database. To repair the
database, find the `mongod` binary on your system that lines up with the
Meteor release you're jumping back to, and run
`mongodb --dbpath your-apps-db --repair`. For example:
```
/my-home/.meteor/packages/meteor-tool/1.6.0_1/mt-os.osx.x86_64/dev_bundle/mongodb/bin/mongod --dbpath /my-app/.meteor/local/db --repair
```
[PR #9632](https://github.com/meteor/meteor/pull/9632)
* The `@babel/plugin-proposal-class-properties` plugin provided by
`meteor-babel` now runs with the `loose:true` option, as required by
other (optional) plugins like `@babel/plugin-proposal-decorators`.