pr-vcptcore-qa-10-09-2026-af48

[vc-ci]

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

---

Note

Low Risk
Manifest-only dependency pin with no application code changes; main risk is deploying the intended Catalog build in QA.

Overview
Automated QA manifest update for VirtoCommerce.Catalog: adds an Azure Blob module entry for VirtoCommerce.Catalog_3.1044.0.zip with explicit Id VirtoCommerce.Catalog, alongside the existing prerelease blob 3.1043.0-pr-906-d339.

Also fixes the AzureBlob Modules JSON structure (closing brace for the prior Catalog PR entry) and normalizes the file’s trailing newline.

^{Reviewed by Cursor Bugbot for commit bd2053f. Bugbot is set up for automated code reviews on this repo. 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.}

^{Reviewed by Cursor Bugbot for commit bd2053f. Configure here.}

[cursor]

Duplicate Catalog module versions added

High Severity

The automated Catalog update added VirtoCommerce.Catalog_3.1044.0.zip without removing the existing VirtoCommerce.Catalog_3.1043.0-pr-906-d339.zip entry. vc-build InstallModules will install both packages, so two versions of the same module get deployed and the platform can fail to load Catalog.

 

^{Reviewed by Cursor Bugbot for commit bd2053f. Configure here.}

[vc-ci]

Closed by stale branch cleanup workflow