https://developer.android.com/agents/skills/play/play-billing-library-version-upgrade/skill

To upgrade the Play Billing Library safely, you need a version-aware migration that detects your current billing API baseline, maps it to the latest stable release, and applies required code refactors for purchases and subscriptions before validating the build.

Migrating Android subscriptions across major Play Billing versions requires synthesizing per-version migration guides into a checklist, refactoring ProductDetails querying, modernizing subscription logic, and running assemble/build/test commands to verify version-specific requirements.

Play Billing migration detects deprecated artifacts like SkuDetails by scanning your project's build config and fallback code, establishing your effective billing API baseline to determine whether a direct or stepped migration path is needed.

You can skip major versions if your project is within two major versions of the target release, choosing a direct migration path; otherwise, the upgrade process migrates two major versions at a time to prevent breakages.

Required code refactors when updating the Play Billing Library include reconnection handling, ProductDetails querying, purchase querying, pending purchase rules, and aligning SDK/compile/min SDK requirements with the target PBL version.

You verify a successful Play Billing Library version upgrade by running build, sync, test, and clean checks, then validating version-specific requirements using a smart checklist to ensure no migration steps were missed.