Bump version to 4.3.0

[oguzkocer]

#711 does not contain any release notes, so I wasn't sure how to handle the CHANGELOG file. I could either:

• Create a 4.3.0 without any release notes
• Don't have any 4.3.0 entry at all

I thought not having the entry made more sense, although neither feels right. I am happy to follow a different approach next time if reviewers have any suggestions. For this time, I have very limited time today to finish the WooCommerce-iOS code freeze and I didn't want this to be the blocker. We can even fix the issue after the fact, it just won't be part of 4.3.0 tag.

Update

I had to update the commit to include the Podfile.lock change.

I ran bundle exec pod install before opening this PR, but the Podfile.lock didn't get updated. I guess I missed something. Sorry about that!

[crazytonyli]

Do you mind adding an entry to the CHANGELOG? It appears there is only one PR that's related to the library.

If I'm not mistaken, here are all the PRs since 4.2.0:

Library update

• Make XMLRPC URL optional when verifying WP.com email and new config for skipping XMLRPC for site discovery #711

The demo app update

• Merge 4.2.0 final to trunk #703
• Demo app walking skeleton #698
• Run bundle exec pod install to track new version in demo app #707
• Prepare demo app for showing WordPressAuthenticator features #705
• Add email login to demo app #706
• Implement existing Google-SignIn flow in the demo app #709

[oguzkocer]

@crazytonyli I've mentioned the situation with the CHANGELOG file in the PR description. Did you miss that by any chance?

[crazytonyli]

No, I saw that. But I noticed there is a 4.3.0 tag, which I think probably unblocked your WCiOS code freeze? And presumed you probably have time to update the CHANGELOG.