pr-vcptcore-qa-02-04-2026-6945

[vc-ci]

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

---

Note

Low Risk
Low risk: updates a single module package reference in backend/packages.json plus minor formatting/newline tweaks; main risk is pulling a different VirtoCommerce.Store build than before.

Overview
Updates backend/packages.json to point VirtoCommerce.Store to the released VirtoCommerce.Store_3.1001.0.zip artifact instead of a PR-specific build.

Also includes minor JSON formatting cleanup (whitespace/array formatting) without functional changes to other module entries.

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

Store module missing PR-specific build identifier

High Severity

The VirtoCommerce.Store BlobName changed from VirtoCommerce.Store_3.1001.0-pr-165-2642.zip to VirtoCommerce.Store_3.1001.0.zip, dropping the PR-specific build suffix. Every other AzureBlob module uses a -pr-NUMBER-HASH suffix, indicating PR-specific builds for QA. The PR description confirms this — it says "from PR undefined undefined", meaning the automation failed to resolve the PR number and hash. The QA environment will deploy the base Store module version instead of the intended PR build.