Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| { | ||
| "Id": "VirtoCommerce.Orders", | ||
| "BlobName": "VirtoCommerce.Orders_3.1003.0-pr-490-ea59.zip" | ||
| "BlobName": "VirtoCommerce.Orders_3.1003.0.zip" |
There was a problem hiding this comment.
Orders BlobName missing PR suffix due to automation failure
High Severity
The VirtoCommerce.Orders BlobName was changed from VirtoCommerce.Orders_3.1003.0-pr-490-ea59.zip to VirtoCommerce.Orders_3.1003.0.zip, dropping the -pr-* suffix. Every other AzureBlob module in this file uses a PR-specific blob name (e.g., -pr-186-2762), and the blob store is vc3prerelease.blob.core.windows.net. The PR description confirms the automation failed — it reads "from PR undefined undefined" where a PR number and name were expected. This likely means the generated blob name is incorrect and may reference a non-existent artifact, potentially breaking the QA deployment.


ci: Automated update vc-module-order from PR undefined undefined
Note
Medium Risk
Updates the deployed
VirtoCommerce.Ordersmodule package reference from a PR build to the3.1003.0release zip, which can change runtime behavior in environments consuming this manifest.Overview
Updates
backend/packages.jsonto pullVirtoCommerce.Ordersfrom the releasedVirtoCommerce.Orders_3.1003.0.zipartifact instead of a PR-specific build.Also includes minor JSON formatting/whitespace adjustments (including EOF newline).
Written by Cursor Bugbot for commit 5f427ab. This will update automatically on new commits. Configure here.