Salesforce API and Toolchain Upgrade Control

Overview

Replace fixed-version guesswork with a complete inventory, compatibility matrix, staged validation, explicit ownership, and reversible consumer migration.

Prerequisites

• Repository and org inventory with API versions, libraries, CLI, metadata, events, packages, and consumers
• Current Salesforce API EOL policy, seasonal release notes, dependency releases, and customer support constraints
• Test environments, representative fixtures, compatibility owner, migration window, and rollback point

Tool Discipline

Use Read, Glob, and Grep to inspect approved repository and evidence files, WebFetch to re-check current first-party Salesforce documentation, and Write or Edit only for secretless plans, fixtures, configuration, and redacted receipts.

Current Contract

Salesforce supports REST API versions for a documented lifecycle and retires older versions after notice. As of this review, versions 21.0 through 30.0 are unavailable, while the current support table must be re-fetched before every migration.