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] [ENG-9175] Update oclif version #2008

Merged

Conversation

radoslawkrzemien
Copy link
Contributor

@radoslawkrzemien radoslawkrzemien commented Aug 17, 2023

Why

https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli

How

Updated versions of oclif package, packages in @oclif/ space (mostly those depending on deprecated @oclif/screen package, as well as dependencies that themselves use oclif and used to depend on older versions

Test Plan

Automated tests

@linear
Copy link

linear bot commented Aug 17, 2023

ENG-9175 Update oclif in EAS CLI

Warning: oclif update available from 3.4.3 to 3.7.0.

…-9175-update-oclif-version

# Conflicts:
#	yarn.lock
Fixed flags for build:version:set and build:version:get commands

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Added getters for build status and distribution type from string flag values

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Fixed flags and args in `analytics`, `config`, `credentials` and `submit` commands

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Added getters for environment secret scope and secret type from string flag value

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Added getters for end outcome from string flag value

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Added getters for requested platform from string flag value

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Copy link

github-actions bot commented Dec 1, 2023

Size Change: +13.2 MB (+31%) 🚨

Total Size: 55.5 MB

Filename Size Change
./packages/eas-cli/dist/eas-linux-x64.tar.gz 55.5 MB +13.2 MB (+31%) 🚨

compressed-size-action

This reverts commit f24e7e5.
Oclif v4 and v3 need node >= v18, so had to downgrade it to v2. v2 has a bug however when importing one of the dependencies which makes it unusable so had to go back to v1

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
oclif/plugin-autocomplete v3 needs oclif/core v3 which needs node >= v18, so had to downgrade it to v2

See: https://linear.app/expo/issue/ENG-9175/update-oclif-in-eas-cli
Copy link

codecov bot commented Dec 1, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (0cd0c8c) 54.18% compared to head (4f542db) 54.18%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2008   +/-   ##
=======================================
  Coverage   54.18%   54.18%           
=======================================
  Files         509      509           
  Lines       18662    18662           
  Branches     3742     3742           
=======================================
  Hits        10110    10110           
  Misses       8531     8531           
  Partials       21       21           

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

@radoslawkrzemien
Copy link
Contributor Author

/changelog-entry chore Update oclif dependencies

@radoslawkrzemien radoslawkrzemien marked this pull request as ready for review December 1, 2023 15:32
Copy link

github-actions bot commented Dec 1, 2023

✅ Thank you for adding the changelog entry!

@radoslawkrzemien
Copy link
Contributor Author

TL:DR I had to abandon upgrading @oclif/core to any version above v1 (current version is v4), I can elaborate more during sync. Current versions of dependencies are the newest non-breaking versions

Copy link
Contributor

@sjchmiela sjchmiela left a comment

Choose a reason for hiding this comment

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

I'm not super familiar with Oclif, but there also should be no breaking changes if you believe semver versioning!

"@expo/prebuild-config": "6.2.5",
"@expo/results": "1.0.0",
"@expo/rudder-sdk-node": "1.1.1",
"@expo/spawn-async": "1.7.0",
"@expo/steps": "1.0.51",
"@expo/timeago.js": "1.0.0",
"@oclif/core": "1.23.2",
"@oclif/plugin-autocomplete": "1.3.10",
"@oclif/core": "^1.26.2",
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we want to switch to ^ versions from strict versions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't see the harm in that, v1 is no longer developed anyway afaik (again, current is v4)

@radoslawkrzemien radoslawkrzemien merged commit b44ba6b into main Dec 4, 2023
9 checks passed
@radoslawkrzemien radoslawkrzemien deleted the @radoslawkrzemien/ENG-9175-update-oclif-version branch December 4, 2023 11:07
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.

2 participants