-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
[BREAKING] Support only compatible platform versions #2285
[BREAKING] Support only compatible platform versions #2285
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #2285 +/- ##
=======================================
Coverage 65.17% 65.17%
=======================================
Files 210 210
Lines 20465 20519 +54
=======================================
+ Hits 13338 13374 +36
- Misses 6005 6022 +17
- Partials 1122 1123 +1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
85fa9d8
to
cc1bbab
Compare
18af151
to
cb800ab
Compare
0df532f
to
82bd9e7
Compare
dfb4d40
to
679f014
Compare
d898eea
to
36a4e89
Compare
We leave only the `latest_compatible` field from the API. This field will have the same meaning the the former `latest_compatible_version`. Meaning that if the `latest_compatible` contains a version it is a release that can be installed. However it might happen that we have newer releases that cannot be installed. If the client is interested to show newer-non-installable-releases, the `releases` field can be used to infer that.
36a4e89
to
14e0d5c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small nit pick.
Incredible work! 👍🏼
Please check if the PR fulfills these requirements
See how to contribute
before creating one)
our contributing guidelines
UPGRADING.md
has been updated with a migration guide (for breaking changes)configuration.schema.json
updated if new parameters are added.What kind of change does this PR introduce?
latest_compatible
field in thecc.arduino.cli.commands.v1.Platform
gRPC message.arduino-cli core install arduino:[email protected]
What is the current behavior?
We always try to install (and show) the latest version even if it contains tools not available for the current os.
What is the new behavior?
We show, install, and upgrade a core only if we're sure that all the tools are available for the current OS. Is possible to install a potentially incompatible version providing a specific version of a core.
Does this PR introduce a breaking change, and is titled accordingly?
yup
Other information