[eas-cli] suggest using eas build:dev when using simulator/emulator dev client configuration

[szdziedzic]

Why

Suggest using eas build:dev if one runs eas build resulting in simulator/emulator dev client build.

How

Add log to suggest using eas build:dev

Test Plan

Tests

[szdziedzic]

• [eas-cli] suggest using eas build:dev when using simulator/emulator dev client configuration #2929 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Subscribed to pull request

File Patterns	Mentions
**/*	@khamilowicz, @sjchmiela, @radoslawkrzemien

Generated by CodeMention

[github-actions]

Size Change: -4.39 kB (-0.01%)

Total Size: 53.4 MB

Filename	Size	Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz	53.4 MB	-4.39 kB (-0.01%)

_{compressed-size-action}

[codecov]

Codecov Report

Attention: Patch coverage is 4.00000% with 24 lines in your changes missing coverage. Please review.

Project coverage is 52.63%. Comparing base (34c307c) to head (a87155c).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
packages/eas-cli/src/commands/build/index.ts	4.00%	24 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2929      +/-   ##
==========================================
- Coverage   52.68%   52.63%   -0.05%     
==========================================
  Files         588      588              
  Lines       23219    23242      +23     
  Branches     4614     4626      +12     
==========================================
  Hits        12231    12231              
- Misses      10954    10977      +23     
  Partials       34       34              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[brentvatne]

let's give it a try!

[brentvatne]

it might also be useful to check for a build with the same profile with a matching fingerprint and let people know about that

[szdziedzic]

it might also be useful to check for a build with the same profile with a matching fingerprint and let people know about that

I added this message at the end of the build process. I believe we would need to add the check at the beginning instead, right?

I believe I can merge this PR the way it is and we can figure out the best way to add the fingerprint check in a separate PR.

[github-actions]

✅ Thank you for adding the changelog entry!