debugging issues around specifying the latest patch release

[devoncarew]

• debugging issues around specifying the latest patch release

Investigation around #107.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[devoncarew]

Note that the build failure here is due to the action now requiring 3.3.0-0 to build, but the dev channel is not yet on a 3.3.0 version. This doesn't effect the behavior of the action itself, just our build validation bot.

[sortie]

I'd throw instead. We didn't intend to support only a 3 value. This case means there was a user error and the intended minor version got lost.

[devoncarew]

Unfortunately, what's happening is the user has entered a 3.0 in their yaml file. That gets converted (by the yaml parser? by the javascript runtime?) into a 3 before we get the value. So all we see here is a 3, and have to infer that what they likely had actually written was a 3.0.

[devoncarew]

Without this workaround we would be able to support values of 3.1, 3.2, ..., but not of 3.0.

[devoncarew]

Thanks for the reviews; updated for review feedback and for a fix from #107 (comment).

[athomas]

FYI, build is still failing because of the 3.3.0-0 SDK requirement. It will start working on Thu when the first 3.3 dev release gets published.