francescotimperi opened a new issue, #41: URL: https://github.com/apache/openserverless/issues/41
Updating the ops cli using 'ops -update` always reports that a newer version of the operator is available and that it can be updated using a specific tasks, e.g. `Welcome to ops! Setting up... Cloning tasks... Enumerating objects: 3661, done. Counting objects: 100% (289/289), done. Compressing objects: 100% (110/110), done. Total 3661 (delta 164), reused 271 (delta 158), pack-reused 3372 Tasks downloaded successfully New operator version detected! Current deployed operator can be updated with: ops update operator` We should change the behaviour to trigger this check only if an active installation is detected -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@openserverless.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
