pr-vcptcore-qa-15-05-2026-6a71

[vc-ci]

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

---

Note

Medium Risk
Updates the VirtoCommerce.PageBuilderModule package reference from a PR build to the 3.1010.0 release zip, which can change runtime behavior depending on module differences. Otherwise changes are formatting-only in backend/packages.json.

Overview
Updates backend/packages.json to pull VirtoCommerce.PageBuilderModule from VirtoCommerce.PageBuilderModule_3.1010.0.zip instead of the previous PR-specific artifact.

Also applies minor JSON formatting/whitespace cleanup (including EOF newline behavior) with no other module version changes.

^{Reviewed by Cursor Bugbot for commit b29b15c. 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 b29b15c. Configure here.}

[cursor]

Automation failure produced wrong PageBuilderModule version

High Severity

The PR description explicitly says "from PR undefined undefined", indicating the automation script failed to resolve the source PR number. As a result, the VirtoCommerce.PageBuilderModule BlobName was changed from a PR-specific prerelease build (_3.1010.0-pr-133-3155.zip) to a plain release build (_3.1010.0.zip). Every other module in the AzureBlob source uses a -pr-{N}-{hash} suffixed build, confirming this QA environment expects PR-specific artifacts. This QA environment will now test the wrong version of PageBuilderModule, potentially missing the changes it was intended to validate — or failing entirely if the release artifact doesn't exist in the prerelease blob container.

 

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