fix: #3615761 Regenerate the lock file so the browser test dependency resolves to @vardot/varbase-e2e

Rajab Natshahrequested to merge
issue/varbase_ai-3615761:3615761-varbase-e2e-lockfile-2.0.x into 2.0.x

Follow-up to #3615761: the switch to @vardot/varbase-e2e updated package.json, but yarn.lock was not regenerated, so the lock still resolved webship-js@2.0.4 from npm and a plain yarn install kept fetching it.

Regenerated with yarn install --mode=update-lockfile. The lock now resolves @vardot/varbase-e2e 2.0.2 and carries no reference to the old package.

The file list shows more than yarn.lock because the switch was squash-merged, so this branch's merge base predates it. The merge result itself changes only yarn.lock; every other file already matches 2.0.x byte for byte.

Checkpoints:

  • File an issue
  • Addition/Change/Update/Fix
  • Testing to ensure no regression
  • Automated unit testing coverage
  • Automated functional testing coverage
  • UX/UI designer responsibilities
  • Readability
  • Accessibility
  • Performance
  • Security
  • Developer Documentation
  • User Guide Documentation
  • Reviewed by human
  • Code review by maintainers
  • Full testing and approval
  • Credit contributors
  • Review with the product owner
  • Release notes snippet
  • Release
Edited by Rajab Natshah

Merge request reports