flexxnn / sequelize-auto-migrations

Migration generator && runner for sequelize
MIT License
258 stars 166 forks source link

Is this package dead? #61

Open cjancsar opened 5 years ago

cjancsar commented 5 years ago

There are PRs open from 2017....

Is there an actively maintained fork?

cjancsar commented 5 years ago

@flexxnn if you are not maintaining this library, what would it take for me to become a contributor/maintainer?

karltaylor commented 5 years ago

@cjancsar You could always fork it and improve

cjancsar commented 5 years ago

@karltaylor that creates a disparity in the community. It is better to focus on maintaining one library then forking...

leonelpena commented 5 years ago

I agree with @cjancsar. I am interested on maintaining this library and I was also thinking of forking since there is no answer from @flexxnn.

karltaylor commented 5 years ago

@karltaylor that creates a disparity in the community. It is better to focus on maintaining one library then forking...

It is always better but not always possible due to unmanaged repositories, it would be good if @flexxnn could open this up to invite collaborators, or if that fails, fork to create a new main repo and direct people there via issues like this 😊

moda20 commented 4 years ago

is there an active fork of this repo ?

mgbiedma commented 4 years ago

It seems that @flexxnn is no longer supporting this package. He has no activity in Github since August (and he used to be quite an active member).

This package does not support Sequelize v5 out of the box and Sequelize v6 is already out as a beta.

I support @cjancsar 's proposal. Maybe it's the time to fork and maintain/improve..

MRVMV commented 4 years ago

you can see this maintained one :) sequelize-mig

matmar10 commented 3 years ago

To anyone still actively using sequelize-auto-migrations, I've made a fork and published it as sequelize-lazy-migrations.

I plan on adding some baseline unit tests, and - once we have a baseline - merging as many PRs as possible opened against this repository.

I'd merge all PRs right away but I am wary of breaking changes without a proper unit test baseline.