v7.0.0 Remove /authorizations endpoint

As the /authorizations endpoint is deprecated now and will be removed in December, we released new version of this library, without it.

v6.0.4 Fix item.save() issue

• Fixes #74

v6.0.3 Product variation support

• Adds product variations to list of supported sub-objects to be able to update product variation for issue #20

see examples, which update variation of first product:

v6.0.2 Updated lodash and qs dependencies

6.0.2

v6.0.1 Updated Sinon to remove vulnerability issues

• Updated Sinon to version 6.1.4

v6.0.0 Dropped support for old node versions

• Only node versions 6, 8 and 10 are now supported
• Updated mocha library dependency to 5.2.0 to remove vulnerability issues

v5.0.0 Removal of pushNotifications endpoint

• Removes old pushNotifications endpoint. Webhooks should be used instead.

Breaking change: proper getUpdates() support

• Previously, when one fetched deals and then did deal.getUpdates() on a specific deal object, it triggered an API request to /v1/deals/:id/updates which is a legacy endpoint, not supported and actually meant to go to full deprecation soon. Instead, the proper endpoint is now used, which is /v1/deals/:id/flow. An exception was needed to the interpretation of the API object structure blueprint.
• tl;dr: /item/:id/flow used instead of /item/:id/updates endpoint is now used when fetching data with .getUpdates() method.

Support for related objects fetching

-Adds support for related objects fetching. In related objects (passed down as the sixth argument when fetching objects, or lists of objects) , Pipedrive API passes down things like pictures of persons, relevant user profile data etc that would be needed to properly render the underlying objects to a human being.
-Since related objects do not represent complete objects, they are not wrapped as collectionItems and thus have to be used as data stubs only. This is intentional by design.

Minor test coverage improvements for client.getAll()

v3.0.6

3.0.6