Fetch and output fingerprints and matching builds for use in continuous deployment workflows.
Usage — Outputs — Examples — Caveats — Changelog
Warning This sub action is still in development and might change without notice. It is not yet ready for use.
continuous-deploy-fingerprint-info is a GitHub Action that fetches fingerprints and matching builds for use in continuous deployment workflows.
- Must have expo-updates set up with a
fingerprintruntime version policy. - Must be configured for EAS Update.
This action is customizable through variables defined in the action.yml.
Here is a summary of all the input options you can use.
| variable | default | description |
|---|---|---|
| profile | (required) | The EAS Build profile to use |
| environment | - | The environment to use for server-side defined EAS environment variables |
| working-directory | - | The relative directory of your Expo app |
| platform | all |
The platform to use (available options are ios, android and all) |
| github-token | github.token |
GitHub token to use when pushing version bump commit (read more) |
And the action will generate these outputs for other actions to do something based on what this action did.
In case you want to reuse this action for other purpose, this action will set the following action outputs.
| output name | description |
|---|---|
| ios-fingerprint | The iOS fingerprint of the current commit. |
| android-fingerprint | The Android fingerprint of the current commit. |
| android-build-id | ID for matching Android EAS Build if one exists for fingerprint. |
| ios-build-id | ID for matching iOS EAS Build if one exists for fingerprint. |
When using the GitHub API, you always need to be authenticated.
This action tries to auto-authenticate using the Automatic token authentication from GitHub.
You can overwrite the token by adding the GITHUB_TOKEN environment variable or add the github-token input.
Before diving into the workflow examples, you should know the basics of GitHub Actions. You can read more about this in the GitHub Actions documentation.
See documentation for the continuous-deploy-fingerprint for how one may use this action.
with ❤️ Expo