[eas-cli] Revert "[1/1][eas-cli] generate eas-update-metadata.json on publish …

[quinlanj]

…(#2158)"

This reverts commit 183fe87.

Why

Sorry for flip-flopping, but it turns out I didn't need to output eas update metadata to a separate file for the sentry/eas-update integration work we were doing, so no one needs it anymore.

Test Plan

• tests still pass

[github-actions]

Size Change: +78 B (0%)

Total Size: 50.2 MB

Filename	Size	Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz	50.2 MB	+78 B (0%)

_{compressed-size-action}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (e9064b7) 54.11% compared to head (7da5473) 54.09%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2187      +/-   ##
==========================================
- Coverage   54.11%   54.09%   -0.01%     
==========================================
  Files         516      516              
  Lines       18815    18809       -6     
  Branches     3771     3770       -1     
==========================================
- Hits        10179    10172       -7     
- Misses       8615     8616       +1     
  Partials       21       21              

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

[quinlanj]

/changelog-entry breaking-change stop generating eas-update-metadata.json on publish

[github-actions]

✅ Thank you for adding the changelog entry!

[rainst]

hi @quinlanj,
currently Bugsnag doesn't support automatic source map upload after running eas update so I made a script that makes a manual submission after an update. The script is relying on dist/eas-update-metadata.json to obtain the bundle ids.

I am currently using [email protected] and it works perfectly, but I realised that this feature was removed with the v7 release, is it possible to add it back since this is holding me back from updating?

thank you :)