feat: add support to override Spin compatibility checks for plugins #780
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Spin plugins state which versions of Spin they are compatible with in their plugin manifest. Currently, Spin checks if the plugin is compatible before allowing it to be installed or executed. If incompatible, the operation fails. This allows overriding that failure with an
--override-compatibility-check
flag. When specified during Spin plugin installs, upgrades and executions, the action will continue even if the plugin is incompatible with the current version of Spin.More context on the decision to add this override can be found in this thread: #735 (comment)