.claude/skills/bump-native-sdk/SKILL.md
Use when upgrading native iOS or Android SDK dependency versions in the AdaptySDK React Native project — bumping Adapty pods version or Android gradle dependency versions
npx skillsauth add adaptyteam/adaptysdk-react-native bump-native-sdkInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Upgrades native Adapty SDK dependencies for iOS (CocoaPods) or Android (Gradle) in the React Native wrapper project.
Ask the user if not provided explicitly (but infer from context when obvious):
ios or androidversion (applies to all three pods)bom_version (adapty-bom) and crossplatform_version (they are independent)Edit react-native-adapty-sdk.podspec — update all three pod dependencies to the same version:
s.dependency "Adapty", "<VERSION>"
s.dependency "AdaptyUI", "<VERSION>"
s.dependency "AdaptyPlugin", "<VERSION>"
Edit android/build.gradle — update two dependency versions:
implementation platform('io.adapty:adapty-bom:<BOM_VERSION>')
implementation 'io.adapty.internal:crossplatform:<CROSSPLATFORM_VERSION>'
bom_version and crossplatform_version are independent and typically differ.
After editing source files, build and test devtools example app. Run all commands from project root:
cd examples/AdaptyDevtools
yarn
yarn update-sdk-full
yarn update-native-modules
yarn — install dependenciesyarn update-sdk-full — rebuild and install local SDK packageyarn update-native-modules — run pod update Adapty AdaptyUI AdaptyPlugin in ios/ dirRun all three steps regardless of platform. update-sdk-full is platform-agnostic, update-native-modules keeps iOS pods in sync.
examples/AdaptyDevtools/ios/Podfile.lock changes are expected and must be included in the commit — they are generated by pod update.
Format: chore: upgrade <platform> SDK to <version>
Examples:
chore: upgrade ios SDK to 3.15.3chore: upgrade android SDK to bom 3.15.2, crossplatform 3.15.6After all changes are verified, remind the user:
Don't forget to update
cross_platform.yamlif the cross-platform protocol version changed. Don't forget to bump the version inpackage.json.
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.