Permission checks enforced on task dependency endpoints

The task dependency endpoints now enforce the same permission checks as the Wrike web interface.

The endpoints below now require the TaskDatesAndDependenciesEdit right on both the predecessor and the successor task, matching the behavior already enforced in the Wrike UI:

Affected endpoints

Create Dependency
Modify Dependency
Delete Dependency

If the caller lacks the right on either endpoint, the request is rejected with HTTP 403 (error: "not_allowed"). Previously, these endpoints verified only that the caller had access to both endpoint tasks and that the tasks were in a valid scheduling state, without checking the TaskDatesAndDependenciesEdit permission.

Action required

Review any integration that creates, modifies, or deletes task dependencies. If your integration relies on a service account, confirm that the account has the TaskDatesAndDependenciesEdit permission and adequate space access. Add handling for 403 not_allowed responses.