Fix/ build action#150
Merged
Merged
Conversation
ManuViola77
approved these changes
Jun 23, 2026
asdolo
approved these changes
Jun 23, 2026
amaury901130
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jira board reference:
What does this do?
Fixes the step ordering in the EAS build GitHub Actions workflow. Moves the
actions/checkoutstep to run beforeexpo/expo-github-action, so that the repo is available on disk when the Expo/EAS setup step executes.Why did you do this?
The
expo/expo-github-actionstep was running beforeactions/checkout, which meant the local.github/actions/setup-node-pnpm-installcomposite action (referenced in a later step) and any repo-relative files were not yet available. Reordering ensures the workspace is fully checked out before EAS tooling is initialized.Who/what does this impact?
Affects all EAS builds triggered via the
eas-build.ymlworkflow (main, staging, qa, development branches). No application code changes.How did you test this?
I tested the workflow
https://github.com/rootstrap/react-native-template/actions/runs/27714374165
https://github.com/rootstrap/react-native-template/actions/runs/27700319882
Notes:
The two revert/test commits (
fix: testing purposes of action+ its revert) are squash candidates before merge — the net change is just the step reorder ineas-build.yml.Screenshots / Previews
N/A — CI workflow change only, no UI impact.