Agent skill · software engineering · jeremylongshore
flexport-upgrade-migration
Upgrade a Flexport REST integration using account version settings and request overrides while tolerating compatible additions. Use when changing the Flexport-Version header, testing a new schema, or responding to added fields and event types. Trigger with: "upgrade Flexport API", "change Flexport version", "handle Flexport schema change".
Why this skill is useful
Adds executable scripts and detailed migration patterns for Flexport API versions that are not publicly documented.
What it needs
Requires bash, grep installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
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 Separate breaking target-version differences from compatible additions that may appear without an account-version switch. Step 3: Harden readers Ignore or preserve unknown optional fields, route unknown enum/event values safely, and fail only when a required invariant is absent. Step 4: Test with overrides Exercise approved read-only calls using the target Flexport-Version header while production remains on its current default. Step 5: Canary one cohort Deploy tolerant code first, switch a bounded read cohort, compare business outcomes, then enable mutations only after reconciliation passes. Step 6: Change default last Coordinate account-default changes after all clients are ready, retain explicit rollback overrides, and verify events plus in-flight operations. Authentication REST calls authenticate with a cached OAuth 2.0 client-credentials Bearer token using audience https://api.flexport.com, or an explicitly accepted broad API key. Use distinct credentials per workload and never log credentials or tokens. MCP calls use the authenticated connection to https://mcp.flexport.com/mcp and remain subject to each tool's documented account permissions. Tool Discipline Use Read and Grep for discovery and evidence. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/flexport-upgrade-migration