Overview

Artifact ID: b9b61a672790afe693aacc9465c3669cf02ebe1429b32128524e752c38f6edd3
Page Name:version
Date: 2018-07-03 20:17:00
Original User: mario
Mimetype:text/x-markdown
Next 6dfc8818efc37f2f8487256c64023938adc4cfd26e3f9e3a85ff9d53d1cd916b
Content

# version:

Each plugin may carry its own version number:

# version: 0.5

Which makes sense as features progress individually of the main application. It's the whole point of plugin systems to provide independent 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: or support: to expand on the current code quality/completion.