pr-vcptcore-qa-07-04-2026-7274

[vc-ci]

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

---

Note

Low Risk
Low risk configuration-only change; main impact is deployment behavior by switching where the VirtoCommerce.Seo module is fetched from and which version is installed.

Overview
Updates module manifest to bump and re-source VirtoCommerce.Seo. backend/packages.json removes VirtoCommerce.Seo (3.1000.0) from the GithubReleases source and adds it to the AzureBlob source as VirtoCommerce.Seo_3.1001.0.zip.

Also includes minor JSON formatting/whitespace adjustments (including EOF newline change).

^{Reviewed by Cursor Bugbot for commit 2ef082a. 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 kicking off a free cloud agent to fix this issue. This run is complimentary, but you can enable autofix for all future PRs in the Cursor dashboard.}

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

[cursor]

Seo module blob likely references nonexistent artifact

High Severity

The VirtoCommerce.Seo module was moved from the GithubReleases source to AzureBlob, but its BlobName (VirtoCommerce.Seo_3.1001.0.zip) lacks the -pr-NUMBER-HASH suffix that nearly every other AzureBlob entry has. The PR description confirms the automation failed: "from PR undefined undefined" — the PR number and identifier were not resolved. This strongly suggests the referenced blob artifact may not exist in Azure storage, which would cause a deployment failure at module download time.

 

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

[cursor]

Bugbot Autofix determined this is a false positive.

The referenced Azure blob VirtoCommerce.Seo_3.1001.0.zip is publicly present in the vc3prerelease/packages container and returns HTTP 200, so this entry does not point to a missing artifact.

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}