chore(ci): remove eas-update job from CI#633
Merged
Ur-imazing merged 1 commit intomainfrom Apr 2, 2026
Merged
Conversation
The EAS Update job was running on all PRs regardless of whether mobile code was affected, causing unnecessary CI failures. Removing it until a better solution is in place. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
🚅 Deployed to the forge-pr-633 environment in forge 4 services not affected by this PR
|
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
1 participant
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.
Summary
eas-updatejob from the CI workflow — it was running on all PRs regardless of mobile changes, causing unnecessary CI issues.Test plan
🤖 Generated with Claude Code