[eas-cli][eas-update] Allow undefined update message

[wschurman]

Why

This was requested for cases where there isn't a VCS and also no update message is manually supplied.

Closes ENG-9633.

How

It is already optional in the GraphQL mutation, so this is just a product decision that we need to deliberately make.

For Reviewers

I think it's worth having a discussion on the UX benefits/costs of this product decision. This PR is meant to just start the discussion, not convey a strong intent to make the change as I'm probably oblivious to potential downsides.

Test Plan

Create an update and don't specify message.

[linear]

ENG-9633 Investigate whether we can make `eas update` message flag optional

[wschurman]

/changelog-entry new-feature Allow undefined update message for EAS Update publishing

[github-actions]

Size Change: -488 B (0%)

Total Size: 55.5 MB

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

_{compressed-size-action}

[codecov]

Codecov Report

Attention: 11 lines in your changes are missing coverage. Please review.

Comparison is base (2dab784) 54.22% compared to head (21d0fa7) 54.21%.

❗ Current head 21d0fa7 differs from pull request most recent head d81d4c8. Consider uploading reports for the commit d81d4c8 to get more accurate results

Files	Patch %	Lines
packages/eas-cli/src/project/publish.ts	12.50%	7 Missing ⚠️
packages/eas-cli/src/vcs/clients/git.ts	0.00%	2 Missing ⚠️
packages/eas-cli/src/vcs/clients/noVcs.ts	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2148      +/-   ##
==========================================
- Coverage   54.22%   54.21%   -0.00%     
==========================================
  Files         509      509              
  Lines       18663    18670       +7     
  Branches     3737     3741       +4     
==========================================
+ Hits        10119    10121       +2     
- Misses       8523     8528       +5     
  Partials       21       21              

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

[quinlanj]

Most of our UI's and tooling rely on people to provide a message to be usable, and we assume most people are using some kind of VCS. No VCS would be a bad user experience, but in the absence of a VCS, we should not be blocking people from publishing.

[wschurman]

That's a good point. Maybe we should only allow this to be empty when there's no VCS?

[wschurman]

/changelog-entry new-feature Allow undefined update message for EAS Update publishing when no VCS

[github-actions]

✅ Thank you for adding the changelog entry!