Skip to content

Conversation

@vc-ci
Copy link
Contributor

@vc-ci vc-ci commented Jan 20, 2026

ci: Automated update vc-module-customer from PR undefined undefined


Note

Updates module source configuration.

  • Adds VirtoCommerce.Customer to AzureBlob with BlobName VirtoCommerce.Customer_3.1000.0.zip
  • Removes VirtoCommerce.Customer from GithubReleases modules list (previously 3.850.0)
  • Minor JSON formatting cleanups in backend/packages.json

Written by Cursor Bugbot for commit 4482471. This will update automatically on new commits. Configure here.

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.Customer",
"BlobName": "VirtoCommerce.Customer_3.1000.0.zip"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Module blob name missing PR suffix from failed automation

High Severity

The VirtoCommerce.Customer module's BlobName value VirtoCommerce.Customer_3.1000.0.zip doesn't follow the established pattern. All other AzureBlob entries use the format ModuleName_Version-pr-PrNumber-Hash.zip, but this entry is missing the -pr-XX-XXXX suffix. Combined with the PR description stating "from PR undefined undefined", this indicates the automation script failed to capture proper PR metadata, and the blob name likely doesn't correspond to an actual artifact in Azure storage.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants