This action uses @expo/fingerprint
to generate a fingerprint of native changes between a current
branch and a target branch. It is similar to Expo's existing fingerprint action
(see Expo's actions repository), however it does not
cache previous fingerprints. We have experience some issues with the caching approach, as our caches
are often invalidated (because of Docker build caches), leading to many unnecessary rebuilds of
TestFlight/internal clients.
Required The name of the profile to use for the fingerprinting. Valid options are:
production
- Uses the supplied git tag to compare the current commit againsttestflight
- Uses the cached "last testflight commit" to compare the current commit againstpull-request
- Uses the base branch of the pull request to compare the current commit against
Required when using production
profile. This should be the tag of the previous commit to compare
against. If it is not supplied - or it is not a valid tag - the action will fail when using production
profile.
This value is automatically set by the action and should not be set manually.
Once a new TestFlight client has been successfully built by GitHub, you should update the cache with the commit hash the build was based on.