-
Notifications
You must be signed in to change notification settings - Fork 37
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
Release v4.0.0. What is the braking change? #79
Comments
Hi! Thanks for the feedback! There are no
I understand it is not fully actually fully SemVer, but I thought the change in default behavior was still merited the major bump. (and to signal that we are now supporting most of the unleash 4.x server features). Was this helpful? I really like your suggestion of using https://keepachangelog.com . I will try to add one soon. |
Hi @rarruda, thanks for your feedback. I am going to close this issue |
Added a CHANGELOG following https://keepachangelog.com/, as per your suggestion! Thanks for the help! |
Hi,
you recently released v4.0.0.
What are the breaking changes a user needs to be aware of when upgrading?
I checked the diff, but it is not obvious.
v3.2.5...v4.0.0
Consider to use the GitHub release feature. A nice way to communicate changes is https://keepachangelog.com
Kind regards
The text was updated successfully, but these errors were encountered: