Ruben Vermeersch

@rkintzi This new error is caused by #53 and is meant to guard you from errors. It's not breakage in that it breaks your code, it now just forbids code...

@KeiichiHirobe hey yes that's a good suggestion, feel free to submit a PR!

Hi, sorry for the late reply. As mentioned in #45, I don't think this functionality has a place in sql-migrate, there's too many different ways to do this and I...

> we use 000001-something.sql 000002-else.sql etc, but the "new" command doesn't care, or even look at the existing naming, and blindly generates a timestamp based template. May have said this...

@Plamen25 that's really not how it's usually done in Go projects. Consider master as stable.

Yeah well, coming from the Node.JS side of things, I respectfully disagree with Mr. Cheney. Now, before we get into philosophical musings, let's consider this: sql-migrate is very stable and...

> when things actually do change, we can't be certain that taking a change won't break our usage of the library without spending extra time validating the changes. Semver doesn't...

Always resisted rolling a release until now cause it's extra work, but things are pretty much stable now. I'll roll a release once I get a chance. On Thu, Dec...

> I forgot to mention, using @latest did not work. > > ```shell > $ go install github.com/rubenv/sql-migrate@latest > package github.com/rubenv/sql-migrate is not a main package > ``` The executable...

I haven't used cert-based auth myself, so I can't really tell what should be added, but I don't think it'll be hard to add. Will happily accept a PR, it's...