upgrading-expo skillA
upgrading-expo is agent-read markdown (skill) from j-star-films-studios/vibecode-protocol-suite: Guidelines for upgrading Expo SDK versions and fixing dependency issues.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
## References - ./references/new-architecture.md -- SDK +53: New Architecture migration guide - ./references/react-19.md -- SDK +54: React 19 changes (useContext → use, Context.Provider → Context, forwardRef removal) - ./references/react-compiler.md -- SDK +54: React Compiler setup and migration guide - ./references/native-tabs.md -- SDK +55: Native tabs changes (Icon/Label/Badge now accessed via NativeTabs.Trigger.\*) - ./references/expo-av-to-audio.md -- Migrate audio playback and recording from expo-av to expo-audio - ./references/expo-av-to-video.md -- Migrate video playback from expo-av to expo-video ## Beta/Preview Releases Beta versions use `.preview` suffix (e.g., `55.0.0-preview.2`), published under `@next` tag. Check if latest is beta: https://exp.host/--/api/v2/versions (look for `-preview` in `expoVersion`) ```bash npx expo install expo@next --fix # install beta ``` ## Step-by-Step Upgrade Process 1. Upgrade Expo and dependencies ```bash npx expo install expo@latest npx expo install --fix ``` 2. Run diagnostics: `npx expo-doctor` 3. Clear caches and reinstall ```bash npx expo export -p ios --clear rm -rf node_modules .expo watchman watch-del-all ``` …
Read the whole file at its exact version.
How to install
mdr add j-star-films-studios/vibecode-protocol-suite/upgrading-expo@v1.0.0mdr add j-star-films-studios/vibecode-protocol-suite/upgrading-expo@sha256:77f75bcd16b4ddf5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_ukkgdwyceflrnleh)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4936 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
j-star-films-studios/vibecode-protocol-suite · 24 stars · license ISC · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ukkgdwyceflrnleh GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/upgrading-expo GET https://markdownregistry.com/api/v1/blob/77f75bcd16b4ddf52087a2956aed05fbdc5efc53ca66183a0a64509b7162d6de
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
More from j-star-films-studios/vibecode-protocol-suite
Every file in j-star-films-studios/vibecode-protocol-suite