-
-
Notifications
You must be signed in to change notification settings - Fork 496
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
Changes in 2.0 #338
Comments
I couldn't find it either. This is the closest info on the reason 2.0 was released I could find: #322 |
Definitely need this. I can't just pull in arbitrary updates w/o knowing what potential effect it will have. Certainly there would be mention if the API surface has been altered. |
As a workaround: If you need info about API changes you can use FuGet: https://www.fuget.org/packages/SqlKata/2.2.0/lib/netstandard1.0/diff/1.1.8-ci-712/ |
No change log at the moment, will try to find a way to automate this for future release, due to limited time/resource to support this. |
If you're not familiar with it, takes a look at https://www.conventionalcommits.org/en/v1.0.0/ If you follow a pattern with your commit messages, it's easier to parse them and automatically maintain release notes. |
Interesting!, I think this is the best solution for now, I will read about it more! |
Is there a changelog somewhere to show what's new in 2.0?
The text was updated successfully, but these errors were encountered: