Skip to content
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

Closed
asherber opened this issue Jan 18, 2020 · 6 comments
Closed

Changes in 2.0 #338

asherber opened this issue Jan 18, 2020 · 6 comments

Comments

@asherber
Copy link
Contributor

Is there a changelog somewhere to show what's new in 2.0?

@lbguilherme
Copy link

I couldn't find it either.

This is the closest info on the reason 2.0 was released I could find: #322

cc @ahmad-moussawi

@mark-at-tusksoft
Copy link

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.

@toburger
Copy link
Contributor

toburger commented Oct 6, 2020

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/
But it is not really a replacement for a changelog.

@ahmad-moussawi
Copy link
Contributor

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.

@asherber
Copy link
Contributor Author

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.

@ahmad-moussawi
Copy link
Contributor

Interesting!, I think this is the best solution for now, I will read about it more!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants