pr-vcptcore-qa-03-04-2026-b029

[vc-ci]

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

---

Note

Low Risk
Low risk manifest-only change updating the VirtoCommerce.Notifications package reference; primary risk is pulling a new module build into the environment.

Overview
Updates backend/packages.json to use VirtoCommerce.Notifications_3.1005.0.zip (replacing the prior PR build) and adjusts its placement within the Azure Blob module list.

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

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

Automation failure produced likely incorrect blob name

High Severity

The VirtoCommerce.Notifications module was updated by automation that clearly failed — the PR description contains "from PR undefined undefined", indicating the script couldn't resolve the source PR. The resulting BlobName VirtoCommerce.Notifications_3.1005.0.zip lacks the -pr-XXX-YYYY suffix that every other module in the vc3prerelease AzureBlob container uses. This release-style version likely doesn't exist in the pre-release blob container, which would cause a deployment failure.