pr-vcptcore-qa-23-02-2026-6033

[vc-ci]

ci: Automated update vc-module-push-messages from PR undefined undefined

---

Note

Low Risk
Config-only change to module sourcing/version pinning; main risk is pulling a different PushMessages build than before.

Overview
Updates backend/packages.json to pull VirtoCommerce.PushMessages from the AzureBlob package source (VirtoCommerce.PushMessages_3.1000.0.zip) instead of GithubReleases (removing the 3.907.0 entry there).

Also includes minor JSON formatting/whitespace adjustments (including a missing newline at EOF).

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

PushMessages source changed to AzureBlob

Medium Severity

VirtoCommerce.PushMessages moved from the GithubReleases source (using Version) to the AzureBlob source (using BlobName). If the blob VirtoCommerce.PushMessages_3.1000.0.zip is not present or naming conventions differ from what the deployment tooling expects for Azure storage, module download/installation can fail at deploy time.

Additional Locations (1)

• backend/packages.json#L194-L197