Use fallback when current version is unavailable

[BalusC]

It's otherwise blocking builds, see also sass/dart-sass#2110

The plugin should fallback to previous version when current version fails to download. If that also fails then fallback further to last successfully used locally cached version.

[cleydyr]

Good catch, @BalusC. I'll address this. Thank you.

[melloware]

you rock @cleydyr !

[cleydyr]

The proposed implementation to make this plugin more resilient is to iterate through each release and each release artifact and check if an artifact name matches what's expected (dart-sass-[VERSION]-[OS]-[ARCH].[EXTENSION]). If there's a matching artifact, we'll use its release as the autodetected version.

Note: the results returned by the GitHub API seem to be sorted by the date of the tag/commit [1], though it's not documented on the API doc itself.

The plugin should not fall back to the locally cached version, as the Dart Sass autodetection is intended to be used in environments with an Internet connection [2], which means it's also able to download at least one version with a matching artifact for all supported os-arch combinations (1.68.0 is one such version). Also, if there was a locally cached release to begin with, it would already be used, and the release download wouldn't be attempted.

[cleydyr]

Issue fixed on version 1.2.0, already deployed and soon to be published on Maven Central.

[melloware]

Confirmed its in Maven Central.

[cleydyr]

Closing this now.

[BalusC]

fab