Running ap_verify on an existing repository after making code changes leads to the pipeline aborting with a "version mismatch". This is a known safeguard in the tasks framework.
However, the exact behavior when this happens is less than desirable: image differencing produces the following message:
imageDifference FATAL: Failed in task initialization: Version mismatch (ap_verify: LOCAL:[redacted]/ap_verify@30c9d872774ef5ed6723132d8256950d88763d4b+af3b3d1ed59abc01ce09bd5993fe60ec vs LOCAL:[redacted]/ap_verify@30c9d872774ef5ed6723132d8256950d88763d4b+0c9df25dfe2f58f65f45a867b570c253; ap_pipe: LOCAL:[redacted]/ap_pipe@159164f38bc8c1532d74b8d3c34863f062b82647 vs LOCAL:[redacted]/ap_pipe@159164f38bc8c1532d74b8d3c34863f062b82647+dc7703a8f6ae9f7f2541452aeac0a47e); consider using --clobber-versions or --no-versions
and then keeps running through source association. This is most likely because image differencing is being run as a command-line task "in continue on any error" mode, so that ap_pipe cannot distinguish successful operation, errors in some data sets, and failure of the task itself.