clarification on when a deploy hook is triggered

[gilzow]

Where on docs.platform.sh should be changed?

https://docs.platform.sh/create-apps/hooks/hooks-comparison.html
https://docs.upsun.com/create-apps/hooks/hooks-comparison.html

https://docs.platform.sh/create-apps/hooks/hooks-comparison.html#:~:text=*%20All%20of%20the%20hooks%20run%20with%20changes%20to%20the%20code%20or%20environment.%20This%20column%20indicates%20which%20hooks%20run%20on%20a%20redeploy%20without%20any%20code%20changes.

https://docs.platform.sh/create-apps/hooks/hooks-comparison.html#:~:text=The%20build%20hook%20runs%20only%20when%20the%20app%20or%20its%20runtime%20(variables%20and%20such)%20have%20changed.%20Redeploys%20with%20no%20changes%20trigger%20only%20the%20post_deploy%20hook.%20If%20you%20need%20the%20build%20hook%20to%20run%2C%20manually%20trigger%20a%20build.

https://docs.platform.sh/create-apps/hooks/hooks-comparison.html#:~:text=Your%20deploy%20hook%20is%20tied,manually%20trigger%20a%20build.

(and the equivalent sections on docs.upsun)

What exactly should be updated?

We need to clarify that there are some circumstances where the deploy hook will run even if no code changes have occurred. Something like

To keep your apps and services up-to-date and secure, we regularly update patch versions of our images. If a new patch version of an image has been released since your last deployment, your next deployment will include this update, and the build and deploy hooks will be run, even if there was no code change. This could for instance happen when the certificate of your environment is automatically renewed. This approach helps to keep your environments up-to-date and safe on a regular basis. Note that, since these updates are patch versions only, the risk of the new image causing regression is minimal, but not totally non-existent.

Additional context

No response