Open lfatty opened 8 years ago
Updated to latest milestone release of ZAP, but that has broken the API. Still debugging this issue.
Any progress on this bug?
Hi @lfatty, yes there has been progress, but we're still debugging the new API that the ZAP milestone introduced, which is taking some time.
@lfatty because of the API incompatibilities we'd have to do a big bang migration and support only the dev branch of ZAP and not the current released version. ZAP's dev branch is not as well tested and might introduce other issues. So we'll only make this change when the next ZAP version is released.
@continuumsecurity, thanks for the update and I am looking forward to the next release of ZAP. Does this mean that some folks will stop using the framework until this issue is resolved?
@continuumsecurity could you provide more details on the API incompatibilities? Wondering if it's an issue on our side.
Please apply the update in order to fix this issue. See link: https://github.com/zaproxy/zaproxy/issues/2745