Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
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.Assets", | ||
| "BlobName": "VirtoCommerce.Assets_3.1002.0.zip" |
There was a problem hiding this comment.
Assets module blob name likely incorrect from failed automation
High Severity
The VirtoCommerce.Assets BlobName changed from VirtoCommerce.Assets_3.1002.0-pr-36-2ce1.zip to VirtoCommerce.Assets_3.1002.0.zip, dropping the PR-specific suffix. Every other module in the AzureBlob source uses a -pr-* suffixed blob name (e.g., -pr-186-2762, -pr-106-ad89). The PR description reads "from PR undefined undefined," indicating the automation script failed to resolve the source PR number and title, which likely caused it to generate a blob name without the expected PR suffix. This artifact may not exist in the prerelease blob storage, potentially causing a deployment failure.
1 participant
ci: Automated update vc-module-assets from PR undefined undefined
Note
Low Risk
Low risk config-only change that updates the
VirtoCommerce.Assetsartifact name/version inbackend/packages.json; potential impact is limited to which module package gets pulled during deployments.Overview
Updates
backend/packages.jsonto switch theVirtoCommerce.Assetsmodule artifact from a PR-specific blob (..._3.1002.0-pr-36-...zip) to the released package (VirtoCommerce.Assets_3.1002.0.zip) and reorders the entry within the Azure Blob modules list. Also includes minor JSON formatting/whitespace adjustments (including EOF newline).Written by Cursor Bugbot for commit e4a06d0. This will update automatically on new commits. Configure here.