pr-vcptcore-qa-23-02-2026-ee76

[vc-ci]

ci: Automated update vc-module-elastic-search-8 from PR undefined undefined

---

Note

Low Risk
Manifest-only changes that alter which ElasticSearch8 module artifact/version gets pulled; risk is limited to potential deployment/runtime mismatch if the new package is incompatible.

Overview
Updates backend/packages.json to source VirtoCommerce.ElasticSearch8 from Azure Blob packages (BlobName VirtoCommerce.ElasticSearch8_3.1000.0.zip) instead of listing it under GithubReleases (previously Version 3.825.0).

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

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

BlobName missing PR suffix from failed automation

High Severity

The BlobName for VirtoCommerce.ElasticSearch8 is VirtoCommerce.ElasticSearch8_3.1000.0.zip, which lacks the -pr-{number}-{hash} suffix that every other AzureBlob entry has. The PR description confirms this: "from PR undefined undefined" indicates the automation script failed to resolve the PR number and commit hash. This likely points to a non-existent blob in the prerelease storage, which would cause a deployment failure.