Plugin manifests does not enforce semver for plugin versions, and the plugins command relies on valid semver.

[mikkelhegn]

While working on spinframework/spin#3656 I noticed two manifests which do not use valid semver:

spin-plugins/manifests/trigger-kinesis/trigger-kinesis@0.1.0.json

Line 4 in a63d6d9

"version": "0.1",

and

spin-plugins/manifests/trigger-kinesis/trigger-kinesis@0.2.0.json

Line 4 in a63d6d9

"version": "0.2",

.

A few possible things we could do:

1. Implement valid semver check in the plugin manifest schema check, by adding a regex pattern from semver.org here:

   spin-plugins/json-schema/spin-plugin-manifest-schema-0.1.json

   Line 24 in a63d6d9

   "version": {

2. To deal with those existing manifest plugins, submit a PR to fix them, and have them pass the new requirement (above)
3. Enforce only parsing true semver in the plugins command for installation (today you can install a non semver compatible version of a plugin if it's "latest", but the CLI flag for selecting an explicit version is strict semver).

Guidance on this is appreciated.