Updated package dependencies

[ravihara]

** READ THIS FIRST! **

Are you implementing a new feature?

No

Requests for new features should first be discussed on the developer forum. This allows the community to gather feedback and assess whether or not there is an existing way to achieve the desired functionality.

If it is determined that a new feature needs to be implemented, include a link to the relevant discussion along with the pull request.

Is this a security patch?

No. It is mainly the package dependency update patch.

Do not open pull requests that might have security implications. Potential security vulnerabilities should be reported privately to [email protected]. Once any vulerabilities have been repaired, the details will be disclosed publicly in a responsible manner. This also allows time for coordinating with affected parties in order to mitigate negative consequences.

If neither of the above two scenarios apply to your situation, you should open a pull request. Delete this paragraph and the text above, and fill in the information requested below.

There is no code change except that, dependencies have been updated to the latest releases and the tests have been run successfully, post update.

Checklist

• [x] I have read the CONTRIBUTING guidelines.
• [ ] I have added test cases which verify the correct operation of this feature or patch.
• [ ] I have added documentation pertaining to this feature or patch.
• [x] The automated test suite ($ make test) executes successfully.
• [x] The automated code linting ($ make lint) executes successfully.

[coveralls]

Coverage remained the same at 99.79% when pulling 453ffbc658534aab12a0c8dea3ea572f9d7b79b7 on ravihara:master into 9de7d6435be8364befda75995c0113879d3b084c on jaredhanson:master.