eas update and eas build created .jsbundle can be different if env vars .eas.json and actions .env vars are different

[mfazekas]

Topic and scope of discussion

continuous-deploy-fingerprint sometimes call eas update if fingerprint matches and eas build if it doesn't.

• eas update picks environment variable form env: set in GitHub actions. docs
• eas build picks environment variables from eas.json docs

This can cause continuous-deploy-fingerprint actions to produce different jsbundle for update vs build.

Motivation

Building different .jsbundle for update vs build can be problematic. And while the expo docs mentions this for EAS Build and EAS Update this can be suprising for continuous-deploy-fingerprint consumers.

Additional context

https://github.com/mfazekas/env-sample demonstrates the issue

Not sure if this can/should be fixed/warned/documented.