[Android][EAS Submit] Warn or block when expo.version is duplicated or lower than latest store version (case: 2.1.0 → 2.0.0 accepted silently)

[firasrg]

Do you understand that any feature requests opened in this repository will be closed?

Yes

[firasrg]

Environment

• EAS CLI: Latest
• eas.json: "appVersionSource": "remote", production build profile uses "autoIncrement": true
• Platform: Android (I think the same issue may happen with iOS)
• Distribution: Production internal Testing
• Managed (Expo) workflow

Summary

I accidentally reverted expo.version from 2.1.0 back to 2.0.0 rather than putting 3.0.0. EAS build + submit succeeded and Google Play accepted both uploads (different versionCodes) without any warning. This led to a confusing situation: Production still showed 2.1.0 to users, while Internal had 2.0.0 (newer code, lower semantic version). There was no CLI or service warning that the human-facing version regressed or duplicated.

Why this matters?

• Play enforces only versionCode; teams often assume expo.version monotonic.
• A mistaken downgrade silently passes CI/CD and creates support confusion (appears like a rollback).
• Harder to correlate crashes / analytics by semantic version when duplicates or regressions occur.

Steps to reproduce

• Build the app with expo.version = 2.0.0 and submit it to store.
• Make some changes then build the app and submit it with expo.version = 2.1.0 (autoIncrement gives versionCode N).
• Make some new changes, change expo.version manually to 2.0.0 (lower) while keeping build profile with autoIncrement: true.
• Run npx eas build --platform android --profile production.
• Submit: npx eas submit -p android --profile production.
• Repeat (produces another artifact: same versionName 2.0.0, higher versionCode N+1).
• Observe no warnings from EAS CLI or service; Play accepts both.

Expected behavior

• Either: CLI warns (non-fatal) that expo.version is <= latest published version (by channel / track).
• Optional stricter mode: fail build/submit unless --allow-duplicate-version flag provided.
• Display last known remote version + candidate version in build summary.

Actual behavior

• Build and submit succeed with no indication of semantic version regression or duplication.

Proposed enhancements

• Add pre-build validation comparing intended expo.version vs remote (since appVersionSource: "remote" already fetches metadata).
• Add config flag in eas.json, e.g.: "versionPolicy": { "android": { "enforceMonotonicVersionName": true } }
• Surface a warning in dashboard + CLI.
• (Nice to have) Offer eas version bump helper that safely increments both semantic version + platform codes.

Please add a warning (at minimum) and optionally a configurable enforcement mechanism to prevent accidental semantic version regressions or duplicates.