pr-vcptcore-qa-13-02-2026-73bd

[vc-ci]

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

---

Note

Low Risk
Config-only change that affects which shipping module package/version is deployed; risk is limited to potential runtime incompatibility if the pinned artifact differs from the previously referenced release.

Overview
Updates backend/packages.json to source VirtoCommerce.Shipping from the AzureBlob feed (VirtoCommerce.Shipping_3.1000.0.zip) instead of pulling VirtoCommerce.Shipping 3.816.0 from GithubReleases.

Also includes small JSON formatting/whitespace adjustments and leaves the file without a trailing newline.

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

Shipping BlobName missing PR suffix from failed automation

High Severity

The VirtoCommerce.Shipping BlobName is VirtoCommerce.Shipping_3.1000.0.zip, which lacks the -pr-NUMBER-HASH suffix that every other AzureBlob module has (e.g., -pr-60-f11e). The PR description confirms the automation failed: "from PR undefined undefined". This likely means the blob doesn't exist in the vc3prerelease container, which would cause module resolution to fail at deployment time. The module was also removed from the GithubReleases source where it previously worked at version 3.816.0.