Thanks for asking! We generate all of our client libraries from an upstream source, so supporting them all at the same time means we currently have a backlog on newer API features. In the meantime, you can use the workaround of using the
post method on the client, i.e. instead of having something like
self.tasks.addDependency(taskId, params, **options)
you can use
self.client.post("/tasks/%s/addDependency" % (taskId), params, **options)
When our libraries are updated the underlying implementation will end up looking very similar to, say,
self.tasks.addProject which you can use for a hint about what the API call directly on our client will look like. You can just do the equivalent 2 lines of code, and replace it with the clearer/nicer one on the next client library release.
Thanks, and we hope to catch up our client libraries to the new dependencies endpoints soon! In the medium term, we’re working to get to a state where our client libraries are easier to keep in sync with API endpoints, so thanks for your patience for now.