pr-vcptcore-qa-13-02-2026-b971

[vc-ci]

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

---

Note

Low Risk
Only updates the module manifest to fetch VirtoCommerce.Notifications from a different source/version; no application code changes, but deployments could be affected if the referenced blob package is missing or incompatible.

Overview
Updates backend/packages.json to change how VirtoCommerce.Notifications is sourced: it is removed from the GithubReleases module list (was 3.832.0) and added to the AzureBlob source as VirtoCommerce.Notifications_3.1001.0.zip.

Also includes minor JSON formatting/whitespace cleanup (including file newline/EOF normalization).

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

Notifications blob name missing PR suffix from failed automation

High Severity

The BlobName for VirtoCommerce.Notifications is VirtoCommerce.Notifications_3.1001.0.zip, which lacks the -pr-N-HASH suffix present in every other AzureBlob entry. The PR description also reads "from PR undefined undefined", indicating the CI automation failed to resolve the source PR number and commit hash. This likely means the blob doesn't exist in the vc3prerelease container, which would cause a deployment failure, or it references an unintended artifact.