The theme of this PR is tidying up some details related to Font Awesome 6--in particular, using the latest version 6 as the default upon activation. Prior to this PR, the plugin worked with Font Awesome 6, both for kits and cdn. However, there were some missing pieces for making it the default, and for showing it as the latest in the version dropdown on the admin settings page.
The key underlying issue is that the symbolic version "latest" that appears in the GraphQL API has been deprecated since the release of Font Awesome 6. With the release of Font Awesome 6, the symbolic versions "5.x" and "6.x" were introduced, corresponding to the "latest version 5" and the "latest version 6," respectively. The deprecated symbolic version "latest" continues to resolve exactly the same as "5.x".
So everywhere that this plugin assumed that there was only one kind "latest" version, that needed to be updated.
A related API change is that FontAwesome::latest_version() is being deprecated. FontAwesome::latest_version_5() and FontAwesome::latest_version_6() are being introduced to correspond to "5.x" and "6.x," respectively. FontAwesome::latest_version() is defined to produce exactly the same result as FontAwesome::latest_version_5().
Thus, the PHP API changes directly mirror the symbolic version changes in the GraphQL API.
Secondarily, this PR updates JavaScript dependencies, to address security notifications from dependabot.
Finally, it includes some additional error reporting for failed requests to the REST API.
Closes #163
Closes #162
Closes #107
TODO:
[x] update JS deps to resolve dependabot alerts
[x] update version dropdown on admin page to have latest 6.x by default
[x] update default options to use version latest 6.x by default
[x] test upgrading from 4.1.1 when the release provider options in the db don't yet include latest_version_6
[x] test upgraded version loading front end with CDN before admin refreshes release metadata
[x] update FontAwesome_Preference_Conflict_Detector to deal with 'latest' or '5.x' or '6.x' symbolic versions
[x] test activation when releases metadata in db is still from previous version
[x] ~test upgrade from options schema v1 schema: 4.0.0-rc13 or earlier, to ensure it upgrades to 6.x by default when no other version is present~
The theme of this PR is tidying up some details related to Font Awesome 6--in particular, using the latest version 6 as the default upon activation. Prior to this PR, the plugin worked with Font Awesome 6, both for kits and cdn. However, there were some missing pieces for making it the default, and for showing it as the latest in the version dropdown on the admin settings page.
The key underlying issue is that the symbolic version "latest" that appears in the GraphQL API has been deprecated since the release of Font Awesome 6. With the release of Font Awesome 6, the symbolic versions "5.x" and "6.x" were introduced, corresponding to the "latest version 5" and the "latest version 6," respectively. The deprecated symbolic version "latest" continues to resolve exactly the same as "5.x".
So everywhere that this plugin assumed that there was only one kind "latest" version, that needed to be updated.
A related API change is that
FontAwesome::latest_version()is being deprecated.FontAwesome::latest_version_5()andFontAwesome::latest_version_6()are being introduced to correspond to "5.x" and "6.x," respectively.FontAwesome::latest_version()is defined to produce exactly the same result asFontAwesome::latest_version_5().Thus, the PHP API changes directly mirror the symbolic version changes in the GraphQL API.
Secondarily, this PR updates JavaScript dependencies, to address security notifications from dependabot.
Finally, it includes some additional error reporting for failed requests to the REST API.
Closes #163 Closes #162 Closes #107
TODO: