Bright Data Contract Migration

Overview

Inventory the exact current behavior before changing dependencies or products. Treat an SDK update, API endpoint change, Browser API rename, and product migration as separate changes with separate rollback boundaries.

Prerequisites

• A pinned current dependency or configuration and documented target contract
• Golden synthetic fixtures plus representative redacted receipts
• A dual-read or feature-flag path and rollback owner

Instructions

Step 1: Build the delta

Read the lockfile, adapter, and runbooks; Grep for x-luminati, old product names, obsolete endpoints, raw vendor response coupling, and undocumented ports.

Step 2: Update one boundary