Flexport Version-Tolerant Upgrade

Overview

Flexport supports account-default version selection plus per-request Flexport-Version overrides. Backward-compatible additions can include attributes, resources, optional parameters, enum values, and event types, so readers and routers must be additive-tolerant.

Prerequisites

• Current account default and every application override
• Endpoint/event inventory with sanitized fixtures
• Target-version diff, owner approvals, canary, and rollback

Instructions

Step 1: Discover effective versions

Record the account default and explicit header behavior for every client; do not assume a hardcoded v2 path determines the contract.

Step 2: Classify changes