You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there are quick fixes for some regressions, the last major update created some BUGs and especially some breaking changes due to the scoped NPM packages :(
You can take a look at what was changed from the pull requests:
Hi @dmytro-gokun. Indeed, the CHANGELOG in master branch does not contain info on these versions. They are described in the CHANGELOG file in the release branch. When release is merged into master, they will be visible there.
@tbozhikov With all respect, i do not think this is a good answer. As a library user, i want changelog/release notes be visible and not hidden in some branch. Thank you.
Activity
Pandishpan commentedon Nov 18, 2019
@dmytro-gokun
I think there are quick fixes for some regressions, the last major update created some BUGs and especially some breaking changes due to the scoped NPM packages :(
You can take a look at what was changed from the pull requests:
#2064
#2071
tbozhikov commentedon Nov 18, 2019
Hi @dmytro-gokun. Indeed, the CHANGELOG in
masterbranch does not contain info on these versions. They are described in the CHANGELOG file in the release branch. Whenreleaseis merged intomaster, they will be visible there.dmytro-gokun commentedon Nov 18, 2019
@tbozhikov With all respect, i do not think this is a good answer. As a library user, i want changelog/release notes be visible and not hidden in some branch. Thank you.
tbozhikov commentedon Nov 19, 2019
@dmytro-gokun
releaseis now merged intomaster, so theCHANGELOGthere is updated.