chore: regenerate lockfile for srvx migration - #4374
vercel[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Rihan Arfan <20425781+RihanArfan@users.noreply.github.com>
|
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
🧪 E2E Test ResultsNo test result files found. |
📊 Workflow Benchmarks❌ The benchmark run for No benchmark results were produced. ℹ️ Metric definitions & methodologyMetrics — All timestamps are deployment-side; runs are triggered in-deployment, so the CI runner and api.vercel.com sit outside every measured window. TTFS = Cold starts stay in the numbers (real bursty-workload latency, inflates P75+); Best is the warm floor. |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Sim WorldSimulated world deterministic testing for races. Traces 🟠 The run produced no summary — see the job log. |
|
No measurements were produced. See the run log. |
| express: | ||
| specifier: ^5.2.1 | ||
| version: 5.2.1(supports-color@10.2.2) | ||
| srvx: |
Regenerates
pnpm-lock.yamlfrom currentmainwith thepackages/webdependency changes from #3193 applied, resolving lockfile conflicts while retaining thesrvxdependency update.Validation:
pnpm install --frozen-lockfile --ignore-scriptswith the #3193 package manifest changes applied.