-
Notifications
You must be signed in to change notification settings - Fork 70
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
deprecation warning for mongodb 3.4 #45
Comments
It's a non-fatal warning, see this: It would be good to have it fixed though... |
I'm sorry to say that but in the last couple of years I have no time, nor interest in maintaining this tool as I haven't been using Mongo for about 4 years now. I think the new maintainer or a hard fork is the way to proceed here. |
Heh ok, understand and didn't realize that
…On Mon, Feb 19, 2018, 2:48 AM Eugene Mirotin ***@***.***> wrote:
I'm sorry to say that but in the last couple of years I have no time, nor
interest in maintaining this tool as I haven't been using Mongo for about 4
years now.
I think the new maintainer or a hard fork is the way to proceed here.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#45 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABF1sllupNGNS6_nU4mUwsfZy0lxxTH8ks5tWSdMgaJpZM4ML7My>
.
|
Fixed in my forked branch. You can point to it via changing your dependency to: |
when I try to run migrations on mongo 3.4 I see this deprecation warnings:
The text was updated successfully, but these errors were encountered: