Skip to content

pr-vcptcore-qa-02-04-2026-edec#5634

Open
vc-ci wants to merge 1 commit intovcptcore-qafrom
pr-vcptcore-qa-02-04-2026-edec
Open

pr-vcptcore-qa-02-04-2026-edec#5634
vc-ci wants to merge 1 commit intovcptcore-qafrom
pr-vcptcore-qa-02-04-2026-edec

Conversation

@vc-ci
Copy link
Copy Markdown
Contributor

@vc-ci vc-ci commented Apr 2, 2026

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


Note

Medium Risk
Updates the referenced VirtoCommerce.Marketing package artifact, which can change runtime behavior at deploy time. Risk is limited to module compatibility/configuration, but should be validated in the target environment.

Overview
Switches the VirtoCommerce.Marketing module in backend/packages.json (AzureBlob source) from a PR build (3.1002.0-pr-261-d9e1.zip) to the released artifact (3.1002.0.zip).

Also includes minor JSON formatting/whitespace cleanup and removes the trailing newline.

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

Copy link
Copy Markdown

@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.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

},
{
"Id": "VirtoCommerce.Marketing",
"BlobName": "VirtoCommerce.Marketing_3.1002.0.zip"
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Marketing module blob likely invalid from failed automation

High Severity

The BlobName for VirtoCommerce.Marketing changed from VirtoCommerce.Marketing_3.1002.0-pr-261-d9e1.zip to VirtoCommerce.Marketing_3.1002.0.zip, losing its -pr-{number}-{hash} suffix. The PR description reads "from PR undefined undefined," indicating the CI automation failed to resolve the source PR details. Nearly every other module in the AzureBlob section carries a PR-specific blob suffix. This blob reference was likely generated incorrectly and may point to a non-existent artifact, which would cause a deployment failure.

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.

1 participant