-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add workflow for bumping eas-build dependencies #2216
Conversation
Size Change: -113 B (0%) Total Size: 51.5 MB
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2216 +/- ##
=======================================
Coverage 54.16% 54.16%
=======================================
Files 516 516
Lines 18814 18814
Branches 3969 3969
=======================================
Hits 10188 10188
Misses 7934 7934
Partials 692 692 ☔ View full report in Codecov by Sentry. |
df92537
to
776bbd4
Compare
@expo/steps
and add a workflow for triggering
⏩ The changelog entry check has been skipped since the "no changelog" label is present. |
@expo/steps
and add a workflow for triggeringThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good
# Why Companion to expo/eas-cli#2216 # How Copied the `turtle-v2` step. # Test Plan I'll only get to test it when a new version is released.
Why
It is currently not possible to use
if: ${ always() }
in Custom Build workflows due to outdated@expo/steps
dependency.How
Added a GitHub workflow, similar to the one we have in
turtle-v2
, which will automatically upgrade all dependencies from theeas-build
repo.Test Plan
#2220