Repository navigation
ci: open a pr to fix expo dependencies when expo doctor fails - #167
Open
devs-rootstrap wants to merge 3 commits into
Open
devs-rootstrap wants to merge 3 commits into
devs-rootstrap wants to merge 3 commits into
Conversation
devs-rootstrap
requested review from
amaury901130,
asdolo and
fernandatoledo
and
a balanced review from Copilot
November 6, 2026 12:08
There was a problem hiding this comment.
🟡 Changes recommended
The failure-only guard prevents cleanup after dependencies are aligned, potentially leaving a generated branch or obsolete PR behind because delete-branch: true only takes effect when the action runs again.
1 open issue
What changed in this PR
Overall Review: ai:minor
Extends the template’s Expo Doctor workflow to propose dependency-alignment fixes automatically, reducing manual maintenance.
Changes:
- Adds weekly scheduled checks and manual execution.
- Adds a default-branch repair job that opens or updates a single dependency-fix PR after Doctor fails.
- Documents the automation, required repository setting, and manual CI-trigger limitation.
| File | Description |
|---|---|
docs/src/content/docs/ci-cd/overview.mdx |
Documents scheduled checks and automatic dependency-fix PRs. |
.github/workflows/expo-doctor.yml |
Adds triggers, the repair job, scoped write permissions, and PR review instructions. |
Review effort: Balanced
fernandatoledo
enabled auto-merge
November 17, 2026 14:10
fernandatoledo
approved these changes
Nov 17, 2026
amaury901130
approved these changes
Nov 19, 2026
This branch has not been deployed
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?
Extends
.github/workflows/expo-doctor.ymlso that outdated Expo SDK dependencies are fixed automatically and proposed as a pull request:scheduletrigger (Mondays at 09:00 UTC) and aworkflow_dispatchtrigger (the workflow header already said it could be run manually, but the trigger was missing).fix-dependenciesjob thatneeds: doctorand only runs when:doctorjob failed,pull_request(push to main/master, schedule or manual run),setup-node-pnpm-installaction, runspnpm expo install --fix(the non-interactive equivalent ofnpx expo install --check) and, ifpackage.json/pnpm-lock.yamlchanged, usespeter-evans/create-pull-request(v8.1.1, pinned to its commit SHA) to open or update a single PR from the fixed branchchore/expo-doctor-fix-dependencies, titledchore: align dependencies with the expo sdk, with a body linking to the failing run and explaining how to review it.contents: write,pull-requests: write) are granted only to the new job; thedoctorjob keeps its current permissions. It uses the defaultGITHUB_TOKEN, so no new secrets are required.Why did you do this?
Expo Doctor frequently fails because Expo dependencies fall behind the installed SDK patch versions. The fix is almost always the same manual routine: run
npx expo install --check, commit the result and open a PR. This automates that routine so the fix PR is ready for review as soon as the problem is detected, either after a push to the default branch or by the weekly scheduled check.Who/what does this impact?
expo-doctor.yml), so they also get the weekly check and the auto-fix PR. No CLI changes were needed.Assumptions / requirements:
GITHUB_TOKENdo not trigger other workflows, so CI checks on the auto-generated PR have to be started by closing and reopening it (or by pushing to it). Using a PAT or GitHub App token to avoid this is out of scope.expo install --fixonly fixes dependency version alignment. If Expo Doctor fails for other reasons, no changes are produced and no PR is opened; those issues still need manual fixes.Layer 2: Risk Classification
Author applies a risk label when opening the PR. When in doubt, escalate.
risk:lowrisk:mediumrisk:highSetup
risk:low,risk:medium,risk:highlabels in the repoHow did you test this?
Verification
yamlpackage);actionlintwas not available in the environment.CI=1 pnpm expo install --checkon currentmasterreports outdated packages (expo,expo-constants,expo-font,expo-localization,expo-router,jest-expo), so the doctor job is expected to fail and the new job to open a PR.CI=1 pnpm expo install --fixwas run locally onmaster: it completed without prompts and only modifiedpackage.jsonandpnpm-lock.yaml(changes discarded afterwards, not part of this PR).pnpm lint,pnpm type-check,pnpm lint:translationsandpnpm test(28 suites, 139 tests) pass.master) and confirm that a PR fromchore/expo-doctor-fix-dependenciesis opened.How to test locally
Notes:
peter-evans/create-pull-requestis pinned to a commit SHA (with the version in a comment) because it runs in a job with write permissions right after dependency install scripts.Screenshots / Previews
Not applicable (CI workflow change).