expo publish updates the AndroidManifest.xml and Expo.plist when using --release-channel

[codylundquist]

Expo Diagnostics:

  Expo CLI 4.9.1 environment info:
    System:
      OS: Linux 5.4 Ubuntu 20.10 (Groovy Gorilla)
      Shell: 5.8 - /usr/bin/zsh
    Binaries:
      Node: 15.8.0 - /tmp/fnm_multishell_4815_1627927203818/bin/node
      Yarn: 1.22.10 - /tmp/fnm_multishell_4815_1627927203818/bin/yarn
      npm: 7.5.2 - /tmp/fnm_multishell_4815_1627927203818/bin/npm
      Watchman: 20210409.063814.0 - /usr/local/bin/watchman
    SDKs:
      Android SDK:
        API Levels: 27, 29, 30
        Build Tools: 28.0.3, 29.0.2, 30.0.2, 30.0.3
        System Images: android-29 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom
    npmPackages:
      expo: ^42.0.3 => 42.0.3 
      react: 17.0.1 => 17.0.1 
      react-dom: 17.0.1 => 17.0.1 
      react-native: 0.64.1 => 0.64.1 
      react-native-web: ~0.13.12 => 0.13.18 
    Expo Workflow: bare

Both of these files are obviously checked into Git. So when I run the expo publish command locally, it updates those files from default to whatever release channel I’m pushing to. Is there a way to not have that happen?

[adamjnav]

Hey @codylundquist, sorry for the delay here. Can you explain the use case for your desired behavior? It seems risky to have to publish to a release channel and have your native files not in sync.

Cheers,
Adam

[codylundquist]

Hi Adam,

I’m running the command in my local dev environment to publish new versions of my app. I realize this should be done in GitHub Actions or another CI environment where everything is ephemeral and it doesn’t matter if those files change. I’m just bringing it up here as a bit of a developer experience issue. Whenever I publish, I also then have to check out those 2 files so that I don’t accidentally check them in. It’s actually not that big of a deal checking in those changes, but they are 99% of the time irrelevant to the current changes that would be in a PR.

Cheers,
cody