# version:

Each plugin may carry its own version number:

# version: 0.5

Which makes sense as features progress independly of the main application. It's the whole point of plugin systems to encapsulate functionality.

  • Often it suffices to use MINOR.MAJOR schemes.

  • For larger plugins the more common SEMVER versioning might make sense still.

  • Patch versions etc. however shouldn't be part of the version: field.

Instead one can use state:, priority: or support: to expand on the current code quality/completion.