pr-vcptcore-qa-02-04-2026-2fb1

[vc-ci]

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

---

Note

Low Risk
Low risk: only updates a module artifact reference in backend/packages.json, with no code changes; main risk is deploying the wrong Notifications build if the version/tag is incorrect.

Overview
Updates backend/packages.json to switch the VirtoCommerce.Notifications module in the AzureBlob source from a PR-tagged artifact (3.1004.0-pr-194-8168) to the released 3.1004.0 zip, along with minor JSON formatting/ordering tweaks.

^{Written by Cursor Bugbot for commit c20dd69. 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 module blob name missing PR build suffix

High Severity

The BlobName for VirtoCommerce.Notifications changed from a PR prerelease build (VirtoCommerce.Notifications_3.1004.0-pr-194-8168.zip) to a plain release version (VirtoCommerce.Notifications_3.1004.0.zip). The PR description explicitly says "from PR undefined undefined," indicating the automation script failed to resolve the PR number and commit hash. Nearly all other AzureBlob modules use the -pr-{number}-{hash} suffix pattern. This likely points to a non-existent blob in the prerelease storage container, which would break deployment.