pr-vcptcore-qa-12-02-2026-408e

[vc-ci]

ci: Automated update vc-module-catalog-personalization from PR undefined undefined

---

Note

Low Risk
Config-only change that alters which CatalogPersonalization artifact is deployed; low risk beyond potential runtime incompatibility if the new module version is not compatible.

Overview
Updates module sourcing in backend/packages.json by moving VirtoCommerce.CatalogPersonalization from the GithubReleases list (previously Version: 3.808.0) to the AzureBlob prerelease feed, pinning it to BlobName: VirtoCommerce.CatalogPersonalization_3.1000.0.zip.

Also includes minor JSON formatting/whitespace normalization and leaves the file without a trailing newline.

^{Written by Cursor Bugbot for commit 7dd3133. This will update automatically on new commits. Configure here.}

[CLAassistant]

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

[cursor]

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

[cursor]

Blob name missing PR suffix from failed automation

Medium Severity

The new VirtoCommerce.CatalogPersonalization entry in the AzureBlob source uses BlobName VirtoCommerce.CatalogPersonalization_3.1000.0.zip, which lacks the -pr-{number}-{hash} suffix that every other blob entry in this prerelease container has. The PR description confirms the automation failed to resolve the source PR ("from PR undefined undefined"). This likely means the referenced blob doesn't exist in the vc3prerelease container, which would cause a deployment failure.