gnezim
265fd33e9d
ci-deploy / build-deploy-test (push) Successful in 3m6s
release-verify.yml: three additions, all targeting the webzavod URL (no gnerim.ru in this workflow — release-verify e2e runs against the customer's deployed environment, not our internal preview). 1. Add /etc/hosts entry — flights-ui.devwebzavod.ru has no public DNS. Operator hosts resolve it via local /etc/hosts to 46.235.186.67. Without mirroring that on the runner every probe fails with "Could not resolve host" (runs 537 + 539). 2. Diagnose customer URL reachability — mirrors ci-deploy's tunnel probe but on the customer URL: surfaces broken /api wiring before the e2e suite spends 30 minutes hitting it. 3. Pre-warm /api cache — same rationale as ci-deploy: the four dictionary endpoints are read on every page load, and the upstream WAF rate-limits per source IP. Warm them once with sleeps so the e2e suite hits the customer's nginx cache, not the upstream WAF. schedule-route-buy-button.spec.ts: rewritten for ci-deploy run 538. The previous version hard-coded the first card on a URL that included today, hitting the "today's earliest flight is < 2h out, buy button hides" edge case. Now scans up to 8 cards looking for the buy button on a fully-future calendar week — proves the strip + button surface without depending on which specific rows are buyable on the day.