How do I install the Sdk Version Bump skill?

Run npx skillmds@latest add appsflyersdk/sdk-version-bump in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sdk Version Bump safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sdk Version Bump?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sdk Version Bump free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sdk Version Bump?

appsflyersdk (@appsflyersdk) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sdk Version Bump by appsflyersdk — Agent Skill

Name: Sdk Version Bump
Author: appsflyersdk

File contents

SDK Version Bump

Use this skill when updating the native Android or iOS SDK version wrapped by the AppsFlyer Unity plugin.

Goal

Perform a safe, consistent version bump across C#, Android, and iOS plugin layers, maintaining both billing library variants.

Workflow

Identify which SDK is being bumped: Android SDK | iOS SDK | both
Locate current versions:
- Version constant in Assets/AppsFlyer/AppsFlyer.cs
- android-unity-wrapper/build.gradle (af-android-sdk, billing library v7/v8)
- iOS podspec or dependency declarations
- CHANGELOG.md
Update the native SDK version in all required places.
Check both billing library variants (v7 and v8) — both must be updated consistently.
Decide whether the Unity plugin version must also be bumped.
Check whether changelog must be updated.
Note that deploy/ .unitypackage files must be regenerated on release.
Summarize: old version, new version, files changed, billing library impact, compatibility risk, validation steps.

What to Check

Android

android-unity-wrapper/build.gradle — af-android-sdk and purchase-connector dependencies (both use gradle.properties variables)
android-unity-wrapper/gradle.properties — VERSION_NAME, VERSION_CODE, ANDROID_SDK_VERSION, ANDROID_PC_VERSION
Assets/AppsFlyer/Editor/AppsFlyerDependencies.xml — purchase-connector androidPackage version
Billing library v7 and v8 build variants — both must be updated
ProGuard rules if new classes are added
AppsFlyerAndroidWrapper.java — version constants if any

iOS

iOS podspec or pod dependency declarations
AppsFlyerDependencies.xml — PurchaseConnector iosPod version (defaults to --ios-sdk-version, override with --ios-pc-version)
README.md and docs/Introduction.md — iOS Purchase Connector line must match iOS SDK version
AppsFlyeriOSWrapper.mm — version constants if any

Unity plugin

Assets/AppsFlyer/AppsFlyer.cs — version constant
CHANGELOG.md
deploy/ .unitypackage files (must regenerate after bump)

Output Format

Return:

Summary
SDK bumped: Android | iOS | Both
Previous version → New version
Billing library variants impacted: v7 | v8 | both
Files updated
Plugin version impact
Changelog impact
.unitypackage regeneration required: Yes | No
Validation steps
Compatibility risk

Rules

iOS Purchase Connector defaults to iOS SDK version but can be overridden independently with --ios-pc-version.
Android Purchase Connector version is independent — pass --android-pc-version to bump-version.sh to update it; omit to leave it unchanged.
Both billing library variants must be updated together.
Do not update only one place if multiple version declarations exist.
.unitypackage files are release artifacts — flag them as needing regeneration.
Prefer a minimal and consistent change set.

---name: sdk-version-bumpdescription: Safely bump the wrapped Android SDK or iOS SDK version in the AppsFlyer Unity plugin, update the plugin version if needed, and validate all related files including both billing library variants.---# SDK Version BumpUse this skill when updating the native Android or iOS SDK version wrapped by the AppsFlyer Unity plugin.## GoalPerform a safe, consistent version bump across C#, Android, and iOS plugin layers, maintaining both billing library variants.## Workflow1. Identify which SDK is being bumped: Android SDK | iOS SDK | both2. Locate current versions: - Version constant in `Assets/AppsFlyer/AppsFlyer.cs` - `android-unity-wrapper/build.gradle` (af-android-sdk, billing library v7/v8) - iOS podspec or dependency declarations - `CHANGELOG.md`3. Update the native SDK version in all required places.4. Check both billing library variants (v7 and v8) — both must be updated consistently.5. Decide whether the Unity plugin version must also be bumped.6. Check whether changelog must be updated.7. Note that `deploy/` `.unitypackage` files must be regenerated on release.8. Summarize: old version, new version, files changed, billing library impact, compatibility risk, validation steps.## What to Check### Android- `android-unity-wrapper/build.gradle` — `af-android-sdk` and `purchase-connector` dependencies (both use gradle.properties variables)- `android-unity-wrapper/gradle.properties` — `VERSION_NAME`, `VERSION_CODE`, `ANDROID_SDK_VERSION`, `ANDROID_PC_VERSION`- `Assets/AppsFlyer/Editor/AppsFlyerDependencies.xml` — `purchase-connector` androidPackage version- Billing library v7 and v8 build variants — both must be updated- ProGuard rules if new classes are added- `AppsFlyerAndroidWrapper.java` — version constants if any### iOS- iOS podspec or pod dependency declarations- `AppsFlyerDependencies.xml` — `PurchaseConnector` iosPod version (defaults to `--ios-sdk-version`, override with `--ios-pc-version`)- `README.md` and `docs/Introduction.md` — `iOS Purchase Connector` line must match iOS SDK version- `AppsFlyeriOSWrapper.mm` — version constants if any### Unity plugin- `Assets/AppsFlyer/AppsFlyer.cs` — version constant- `CHANGELOG.md`- `deploy/` `.unitypackage` files (must regenerate after bump)## Output FormatReturn:- Summary- SDK bumped: Android | iOS | Both- Previous version → New version- Billing library variants impacted: v7 | v8 | both- Files updated- Plugin version impact- Changelog impact- `.unitypackage` regeneration required: Yes | No- Validation steps- Compatibility risk## Rules- **iOS Purchase Connector defaults to iOS SDK version** but can be overridden independently with `--ios-pc-version`.- **Android Purchase Connector version is independent** — pass `--android-pc-version` to `bump-version.sh` to update it; omit to leave it unchanged.- Both billing library variants must be updated together.- Do not update only one place if multiple version declarations exist.- `.unitypackage` files are release artifacts — flag them as needing regeneration.- Prefer a minimal and consistent change set.

Frequently asked questions

Sdk Version Bump