Repository navigation
test(expo): reuse the e2e native build when only JS changed - #10384
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
🦋 Changeset detectedLatest commit: a4ed6a0 The changes in this PR will be included in the next version bump. This PR includes changesets to release 0 packagesWhen changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/electron
@clerk/electron-passkeys
@clerk/eslint-plugin
@clerk/expo
@clerk/expo-biometrics
@clerk/expo-google-signin
@clerk/expo-native-components
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/hono
@clerk/localizations
@clerk/mosaic
@clerk/nextjs
@clerk/nuxt
@clerk/react
@clerk/react-router
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/ui
@clerk/upgrade
@clerk/vue
commit: |
Description
Expo's fingerprint in SDK 58 reports native packages as
packagesources, which the e2e CLI could not read. Every run then fell back to hashing the whole fixture lockfile, so the kept native build missed whenever any npm package changed, and each Version packages update rebuilt the app natively. The CLI now reads apackagesource by its name and version, so the native build is reused when only JS changed.Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change