Publish expo sdk version

[marketbox]

We are migrating to SDK 40 but still supporting SDK 38 in prod.

We are attempting to push a bug fix to prod. We need to publish to SDK 38 for a OTA fix.

When we enter expo publish --release-channel prod we see:

Accessing credentials for in project

› Expo SDK: 40.0.0
› Release channel: prod
› Workflow: Managed

These are the values in our package.json

"expo": "^38.0.10",
"react-native": "https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz",

Why is our publish using SDK 40 and how can we continue to use SDK 38 until we are completed with testing for SDK 40?

Thanks!

[adamjnav]

Hey @marketbox, can you run expo diagnostics and share what is printed out here? Does the same thing happen with a different project (if you have others you’re able to test with)?

Cheers,
Adam

[marketbox]

Thanks. We only have the one project.

Here is the output from expo diagnostics

Expo CLI 4.2.1 environment info:
System:
OS: Windows 10 10.0.18363
Binaries:
Node: 12.18.2 - C:\Program Files\nodejs\node.EXE
npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
IDEs:
Android Studio: Version 4.0.0.0 AI-193.6911.18.40.6626763
npmPackages:
expo: ^38.0.10 => 40.0.1
react: 16.11.0 => 16.13.1
react-dom: 16.11.0 => 16.13.1
react-native: https://github.com/expo/react-native/archive/sdk-38.0.2.tar.gz => 0.63.2
react-native-web: ~0.11.7 => 0.13.18
react-navigation: ^4.2.1 => 4.4.4
Expo Workflow: managed

[marketbox]

I should note… I think the problem lies in the fact that we have upgraded expo on a different git branch. When we checkout our master (prod) branch, it seems to be impacted by the fact we have upgraded expo on our dev branch.

[marketbox]

@adamjnav Can you advise on how to proceed? This seems to be a bug in Expo.