Based on an issue faced by a user, it was suggested we include @expo/metro-config in deep dependency version checking, to check any case where this package is the wrong version, not just direct installs.
How
Added @expo/metro-config to the staging API with et update-versions -k 'relatedPackages.@expo/metro-config' -v '~0.10.0'.
Updated Doctor to respect EXPO_STAGING=1 for API calls, so then we could test the additional related package in the API.
Added @expo/metro-config to the existing list of deep dependency version checks
Follow-up after merge
Update release documentation to note that we should update the @expo/metro-config version here.
Update the endpoint on production
Test Plan
Not a perfect check, because installing @expo/metro-config already results in the warning from npx expo install --check, but you can see here now it also triggers the deep dependency check:
Why
Based on an issue faced by a user, it was suggested we include
@expo/metro-configin deep dependency version checking, to check any case where this package is the wrong version, not just direct installs.How
@expo/metro-configto the staging API withet update-versions -k 'relatedPackages.@expo/metro-config' -v '~0.10.0'.EXPO_STAGING=1for API calls, so then we could test the additional related package in the API.@expo/metro-configto the existing list of deep dependency version checksFollow-up after merge
@expo/metro-configversion here.Test Plan
Not a perfect check, because installing
@expo/metro-configalready results in the warning fromnpx expo install --check, but you can see here now it also triggers the deep dependency check: