"Up" non-zero return value about migrate-mongoose HOT 7 CLOSED

@ertanden that's a good insight. I guess I'll have to separate the return value between the CLI usage and the API usage

from migrate-mongoose.

Here's a pull-request: #20

from migrate-mongoose.

Hi Guys did you plan to merge the #20 I want to use this on my CI, currently my workaround is:

"migrate": "migrate up || exit 0"

from migrate-mongoose.

@rkmax The problem with that is that it won't know when the migration actually failed.

from migrate-mongoose.

Don't hold your breath, looks like this project is abandoned

from migrate-mongoose.

Fixed in 4.0.0 thank you, everyone for your contributions!

from migrate-mongoose.

This still seems to be broken. I have this in my package.json:

"dependencies": {
  "migrate-mongoose": "^4.0.0"
},
"scripts": {
  "migration": "migrate"
},

So that I can run npm run migration up, etc. However, up still fails with exit status 1 if there are no migrations:

> npm run migration up

Synchronizing database with file system migrations...
There are no pending migrations.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] migration: `migrate "up"`
npm ERR! Exit status 1

Am I missing something here?

EDIT:
Windows also reports exist status 1:

$ node_modules\.bin\migrate up
Synchronizing database with file system migrations...
There are no pending migrations.

$ echo %errorlevel%
1

Node v10.15.2

from migrate-mongoose.