Pending changes are still visible even after deployment of set changes

[JosRaedts]

A brief description of the issue goes here.

On the screenshot below, we still see that changes are pending between our staging environment and our live environment, even after we've done a deployment from our staging to live environment (if we compare the file git history, the last commit id is equal on both git repositories.

We have opened a ticket on the Umbraco Cloud portal and they mention that it's something that developers are already looking at, so I'm just adding this issue on Github to track the progress.

It's not a blocking issue, but it's confusing to say the least. It doesn't affect the environments in any way, shape or form.

Reproduction

It's not reproducible by specific steps. We've encountered it a few times in the past and it seems to occur randomly at best when you deploy from Development to Staging and from Staging to Live. (it seems that it only is visible though between Staging and the Live environment).

Specifics

• We're using the latest version of V15 (15.4.1)
• We're running our Umbraco instance on Umbraco Cloud
• We are using the default Umbraco Cloud Portal functionality to deploy our changes from lower environments to higher environments

Steps to reproduce

1. Deploy changes from Staging to Live
2. If the deployment is successful and seemingly at random, the pending changes between Staging and Live are still visible

Expected result

The pending changes block becomes invisible if there aren't any changes between the Live and Staging environment

Actual result

Pending changes between Staging and Live are still visible