pr-vcptcore-qa-14-02-2026-4013

[vc-ci]

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

---

Note

Low Risk
Config-only change that adjusts which Marketing module artifact/version is deployed; main risk is deploying an unintended module build if the blob reference is wrong.

Overview
Updates environment package manifest to pull VirtoCommerce.Marketing from the AzureBlob feed (VirtoCommerce.Marketing_3.1000.0.zip) instead of GithubReleases (removing the previous 3.826.0 entry).

Also includes minor JSON formatting/whitespace cleanup and leaves backend/packages.json without a trailing newline.

^{Written by Cursor Bugbot for commit 2544861. 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]

Marketing module BlobName missing PR suffix from automation failure

High Severity

The new VirtoCommerce.Marketing entry in the AzureBlob source has BlobName of VirtoCommerce.Marketing_3.1000.0.zip, which lacks the -pr-NUMBER-HASH suffix that every other AzureBlob module uses (e.g., -pr-60-f11e.zip). The PR description confirms this: it says "from PR undefined undefined", indicating the automation failed to resolve the PR reference. This likely points to a non-existent blob in the prerelease storage container, which would cause a module installation failure in the QA environment.