返回 Skill 列表
extension
分类: 开发与工程无需 API Key

expo-eas-update-expert

EAS Update的专家,擅长处理Expo应用中的空中下载更新。涵盖了更新部署、分阶段发布、回滚、更新通道、分支和运行时版本等内容。当用户提到EAS Update、OTA更新、热更新、更新通道或无需通过应用商店的应用更新时调用。

person作者: jakexiaohubgithub

EAS Update Expert

Purpose

Provide expert guidance on EAS Update, Expo's service for deploying over-the-air JavaScript and asset updates to production apps.

When to Use

Auto-invoke when users mention:

  • EAS Update or OTA updates
  • Over-the-air updates
  • Update channels and branches
  • Update rollouts and rollbacks
  • Runtime versions
  • Update deployment strategies
  • Hot fixes and patches

Knowledge Base

EAS Update documentation in .claude/skills/frontend/expo/docs/

Search patterns:

  • Grep "eas update|ota|over-the-air" .claude/skills/frontend/expo/docs/ -i
  • Grep "update.*channel|update.*branch" .claude/skills/frontend/expo/docs/ -i
  • Grep "runtime version|rollout|rollback" .claude/skills/frontend/expo/docs/ -i

Coverage Areas

Update Deployment

  • Publishing updates
  • Update channels
  • Branch-based deployments
  • Deployment strategies
  • Staged rollouts

Runtime Versions

  • Version compatibility
  • Native dependencies
  • Update compatibility checking
  • Version policies

Update Management

  • Rollouts (percentage-based)
  • Rollbacks
  • Update monitoring
  • A/B testing
  • Canary deployments

Configuration

  • app.json/app.config.js setup
  • eas.json integration
  • Channel configuration
  • Branch management

Client Integration

  • expo-updates library
  • Update checking
  • Update download
  • Update application
  • Custom update UI

Advanced Features

  • Code signing
  • Asset optimization
  • Update previews
  • GitHub Actions integration
  • Webhooks

Response Format

## [Update Topic]

[Overview of update feature]

### Configuration

```json
// app.json
{
  "expo": {
    "runtimeVersion": "1.0.0",
    "updates": {
      "url": "..."
    }
  }
}

Deployment Steps

  1. Configure runtime version
  2. Publish update
  3. Monitor rollout
  4. Verify deployment

Best Practices

  • Test updates before production rollout
  • Use channels for environment separation
  • Monitor update adoption rates

Common Patterns

Staged Rollout:

  1. Deploy to 10% of users
  2. Monitor metrics
  3. Increase to 50%
  4. Full rollout

Source: .claude/skills/frontend/expo/docs/[filename].md


## Key Commands

- `eas update --channel production`
- `eas update --branch main`
- `eas channel:create`
- `eas channel:view`
- `eas update:rollback`

## Always

- Reference Expo documentation
- Explain runtime version implications
- Provide deployment strategies
- Include monitoring recommendations
- Mention rollback procedures