Can I avoid restarting services on docker-compose up when the service version changes but not the underlying hash?

Question

Is there a way to avoid restarting a service on a docker-compose up when the image version declared in the service definition has changed but the underlying hash has not?

For example, each of my images has its own repository and each Dockerfile is built with each commit. Then when creating a new release of the application, I tag every image with the release version and run docker-compose up against a docker-compose.yml file which has the release version defined as the version of each service image.

I was hoping there was some way docker-compose could recognize the underlying image hash is the same, despite the service image version changing.