versioning

Manage the runtimeVersion fingerprint in Expo apps for safe OTA updates.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/anicca-labs/claude --skill versioning-anicca-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: versioning
Source: https://github.com/anicca-labs/claude/tree/main/plugins/expo-rn-plugin/skills/versioning
Command: npx skills add https://github.com/anicca-labs/claude --skill versioning-anicca-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps manage versioning in Expo apps to ensure Over-The-Air (OTA) updates work safely and reliably.

Core Features & Use Cases

  • RuntimeVersion Fingerprint Management: Offers guidance on how to manage runtimeVersion fingerprints to ensure OTA updates apply correctly.
  • OTA Safety: Ensures that OTA updates are safe to apply without breaking the app.
  • Use Case: When setting up automated version/build-number bumping for an Expo app, or when troubleshooting why an OTA update is not reaching devices.

Quick Start

Use the versioning skill to configure your project to use 'fingerprint' policy for runtimeVersion in your Expo app.

Frequently Asked Questions about versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure Expo runtimeVersion fingerprint for OTA updates?

Expo OTA updates fail to reach devices when the runtimeVersion fingerprint mismatch occurs. Managing the fingerprint policy ensures updates only apply to compatible native code builds, preventing broken app states.

What is runtimeVersion fingerprint management in Expo apps?

Use the fingerprint policy for runtimeVersion to configure your Expo project. This policy automatically generates fingerprints based on native code and configuration changes to ensure OTA safety.

Can I use fingerprint policy for runtimeVersion with automated version bumping in Expo?

Yes, the fingerprint policy supports automated version and build-number bumping in Expo apps. It manages the interaction between marketing version bumps and OTA fingerprints to maintain update safety.

Why does my Expo OTA update not reach devices after a version bump?

Expo OTA updates require a fingerprint policy that matches the native code state. This Skill configures runtimeVersion management to ensure updates only apply when the fingerprint is compatible.