prepare release 1.10.0

[shivam2680]

Description

1. Added change-log for latest release
2. bumped up version to 1.10.0

[jackyhu-db]

can you bump the minor version as this change the property name

[kravets-levko]

@jackyhu-db If I correctly understand recent changes, clientId property is still working as before, but now produces warning. If yes - then changing the build number is totally correct, because the release doesn't break library behavior (yet). You'd have to change minor number when you completely remove clientId.

Also, if it works as I think - there is another advantage for changing build number: most users will receive this release (because npm by default installs dependencies with ^ which allows build number changes), and they'll actually see the warning before you actually remove the clientId completely.

[jackyhu-db]

@jackyhu-db If I correctly understand recent changes, clientId property is still working as before, but now produces warning. If yes - then changing the build number is totally correct, because the release doesn't break library behavior (yet). You'd have to change minor number when you completely remove clientId.

Also, if it works as I think - there is another advantage for changing build number: most users will receive this release (because npm by default installs dependencies with ^ which allows build number changes), and they'll actually see the warning before you actually remove the clientId completely.

@kravets-levko minor version also has to be backward compatible, the difference between patch and minor version is if the change is a bug fix and client does not have to do nothing to adopt this change. Here we added a new property that is going to replace the old one. It is like backward compatible interface change and client has to make change in their code to use it, so I would prefer to use minor version so people is aware of this change.