Index of every page on this site: llms.txt
All skills
neha avatar

/release-and-updates

@eb9f097
Run it yourself

Ship React Native release builds, store binaries, and over-the-air JavaScript updates safely. Use when cutting a release, publishing to a store, or shipping an OTA bundle.

Use this Skill: https://skilld.dev/gh/neha/rn-developer-skills/release-and-updates

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈48 tokens for metadata: the name and description. ≈619 when used: this file.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈193 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Release and Updates Skill

Applicability

  • Platforms: iOS and Android
  • React Native: 0.76+ (New Architecture interop assumed unless a checklist item says otherwise)

When to Use

  • Cutting a build for TestFlight, Play testing, or a store
  • Changing version or build numbers, API environments, or signing
  • Shipping JavaScript over the air without a store binary

Severity

  • Merge-blocking: a release binary this diff configures still talks to staging, or an over-the-air bundle ships a change that needs new native code.
  • Should-fix: listing copy and rollout notes.

Guidance

Store binary

  • The release build talks to the production API and does not include dev-only menus or logs
  • Secrets and tokens are not embedded in the JS bundle or the native project (see security)
  • Version name and build number both increase, and the store listing matches the binary that was tested
  • Debug symbols or source maps for this build are retained so crashes can be read (see observability)
  • The privacy disclosure matches what the binary actually collects

Incorrect:

Release scheme still uses the staging API host baked in at build time

Correct:

The release configuration selects the production host, and a smoke test on the release binary confirms it

Over-the-air updates

  • An OTA bundle is published only for native binaries it is compatible with
  • A native change (new module, permission, or SDK) ships in a store binary, not only in an OTA bundle
  • A bad bundle can be rolled back, and the client does not apply a bundle from a different app or environment
  • An update is not forced in the middle of a payment, form submit, or other non-idempotent action

Anti-Patterns

Anti-Pattern Risk Fix
One OTA channel for staging and production Staging JS runs against production users Separate channels per environment
Shipping a new native module as JavaScript only Crash on launch for users who have not updated the binary Gate the feature on a native version check and ship a store build

Pitfalls

  • A debug build hiding a release-only crash (Hermes, minification, missing env var) is the usual surprise. Smoke the release binary.
  • Users on an old binary keep receiving OTAs until the compatibility range excludes them. Exclude them when the JS expects new native code.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts9d3 checks · Risk SAFE
  • Gen Agent Trust Hub9d

    This skill is a documentation-only resource providing checklists and best practices for React Native release management. It contains no code, executable scripts, or network operations, and it promotes secure secret management.

  • Socket9d

    No alerts

  • Snyk9d

    Risk: LOW · No issues

Signed by skilld at eb9f097. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Steadyupdated 2 months ago
version
1.0.1
platforms
[
  "ios",
  "android"
]
react-native-version
0.76+
Other metadata
tags
[
  "react-native",
  "release",
  "ota",
  "store"
]

README badge

README badge for neha/rn-developer-skills/release-and-updates