Open eqtr-ab opened 1 week ago
It may also be worth noting that this same deployment failed with a "package would be downgraded" error, despite there being no such downgrade - we upgraded to 13.4.0 earlier and successfully deployed this before these issues started occurring. The packages referenced by the error message already have the correct version.
Cannot apply update because the following packages would be downgraded: Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj.
&se=2024-07-09T09%3A04%3A42Z&sr=b&sp=r&sig=23LD2MyD5YkR8bpHYXWXGYee96Ofod32xBl5vM0B2qo%3D
info: Received HTTP response headers after 98.3815ms - 200
info: End processing HTTP request after 100.0793ms - 200
info: Executed step: Download update
info: Executing step: Extract Update
info: Extracting zip /app/work/Update.zip to /app/work/Update
info: Executed step: Extract Update
info: Executing step: Checking versions
fail: Update failed with message: Cannot apply update because the following packages would be downgraded: Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj.
fail: Error executing step: Umbraco.Cloud.Deployment.UpdateExecutor.Umbraco.Steps.CheckVersions Cannot apply update because the following packages would be downgraded: Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/VistaHealth.Core/VistaHealth.Core.csproj. Package: Umbraco.Cms, Version: 13.4.0, Project file: /repository/src/VistaHealth/VistaHealth.csproj.
info: Publishing update failed event
info: Executing step: Delete updating marker
info: Start processing HTTP request DELETE https://[snip].umbraco.io/api/vfs/site/locks/updating
info: Sending HTTP request DELETE https://[snip].umbraco.io/api/vfs/site/locks/updating
info: Received HTTP response headers after 146.6575ms - 200
info: End processing HTTP request after 148.7358ms - 200
info: Executed step: Delete updating marker
Edit - I have opened a separate issue for the above, #778.
To confirm, the changes reflected in the first run of the "See diff content" stage of the Azure CI/CD pipeline were committed to our repo at this point, as shown below:
What we are confused/concerned about is the repeated attempts to bring back the same changes in subsequent deployments. We have carried out a second deployment since then, and the same issue occurred.
Hi, I opened a ticket through Umbraco support for this issue and was told to request updates here. Has this been looked at yet? We are hoping to avoid further occurrences of this issue to maintain the integrity of our deployment process.
Issue description
Hi,
We have faced a reoccurring issue since the start of our Umbraco Cloud project using the CI/CD scripts supplied for Azure pipelines by Umbraco. See these logs for two separate deployment attempts, both attempting to bring down the same change to our repo with the second one failing:
Job 0.0.119 (05/07)
See diff content:
Apply git patch to branch:
In this run, the dictionary change has been successfully brought down and applied to the repo in Azure.
On the next run, it attempts to bring down the same change, and produces an error:
Job 0.0.120 (08/07):
See diff content:
Apply git patch to branch: