What are the immediate next steps I should take?

Web: Test version 202510.1.0 of the Web SDK with TCF 2.3 changes, then republish your CMP after the Fall release.

Mobile & CTV: Upgrade to OneTrust’s next-generation SDKs, request the feature for TCF 2.3, and republish once you are ready to move to TCF 2.3.

API: If utilizing the TCF encode endpoint, review with your partners if they are ready to accept 2.3 strings.

All implementations: Align with vendors, confirm legal bases are set, and validate consent signals.