Evidence-linked playbook

SDK major and security upgrade

Use this guide when a major SDK version or security-related dependency change needs controlled validation before release.

  1. 1

    Read official upgrade notes

  2. 2

    Upgrade dependencies in isolation

  3. 3

    Resolve compile and runtime changes

  4. 4

    Ship with monitoring

Migration principles

Start from the provider's current contract, test representative workloads, and keep a rollback boundary until the new behavior is observed in production.

The evidence list below is refreshed from approved public events. It links each guide to the official source observations available today.

Current official evidence

Loading official evidence…

Apply this to your stack