Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[eas-cli][eas-json] remove Intel resource class related code #2093

Merged
merged 3 commits into from
Oct 19, 2023

Conversation

szdziedzic
Copy link
Member

Why

We no longer have Intel Macs in our fleet.

How

Clean up Intel resource class related code

Test Plan

Tests, test manually

@szdziedzic szdziedzic marked this pull request as ready for review October 18, 2023 12:04
@codecov
Copy link

codecov bot commented Oct 18, 2023

Codecov Report

Merging #2093 (b5d3931) into main (14980fe) will increase coverage by 0.10%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main    #2093      +/-   ##
==========================================
+ Coverage   54.05%   54.14%   +0.10%     
==========================================
  Files         509      509              
  Lines       18665    18624      -41     
  Branches     3935     3922      -13     
==========================================
- Hits        10088    10083       -5     
+ Misses       7886     7854      -32     
+ Partials      691      687       -4     
Files Coverage Δ
packages/eas-cli/src/build/runBuildAndSubmit.ts 21.67% <ø> (ø)
packages/eas-cli/src/commands/build/resign.ts 30.00% <ø> (ø)
packages/eas-json/src/build/schema.ts 100.00% <ø> (ø)
packages/eas-json/src/build/types.ts 100.00% <ø> (ø)
packages/eas-cli/src/build/build.ts 22.00% <0.00%> (+2.07%) ⬆️
packages/eas-cli/src/build/utils/resourceClass.ts 26.67% <0.00%> (+1.67%) ⬆️

/**
* @deprecated use M_MEDIUM instead
*/
M1_EXPERIMENTAL = 'm1-experimental',
/**
* @deprecated use M_MEDIUM instead
*/
M1_MEDIUM = 'm1-medium',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about… you know what I'm thinking?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I think that we can't simply remove it, because when we originally introduced the M1 resource class, the way to use it was to set m1-medium in their eas.json (currently we recommend m-medium so you don't have to distinguish between M1, M2 and so on). That's why many people still have this value in their eas.json to this day. If we remove it, this change will break their builds.

I mean it's been deprecated for a while and we are printing a deprecation warning if you use it. So maybe we can do it? I don't know, it's a hard call. What do you think?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't remove it (yet), unless that CLI warning includes a 'do you want us to update your eas.json for you' step.

@github-actions
Copy link

github-actions bot commented Oct 18, 2023

Size Change: -1.16 kB (0%)

Total Size: 42.6 MB

Filename Size Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz 42.6 MB -1.16 kB (0%)

compressed-size-action

@szdziedzic szdziedzic requested a review from sjchmiela October 19, 2023 08:23
@szdziedzic szdziedzic force-pushed the @szdziedzic/remove-intel-related-code branch from 5f4912f to 539d161 Compare October 19, 2023 09:31
@szdziedzic
Copy link
Member Author

/changelog-entry chore Clean up Intel resource classes code after their deletion

@github-actions
Copy link

✅ Thank you for adding the changelog entry!

@szdziedzic szdziedzic merged commit e8df9cd into main Oct 19, 2023
9 checks passed
@szdziedzic szdziedzic deleted the @szdziedzic/remove-intel-related-code branch October 19, 2023 10:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants