You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently multiple or all plugins rely directly on remote main branches of the scripts they are wrapping.
Building the same plugin version may therefore lead to changed plugin behaviour on script change.
Suggested changes:
point to a stable version of the script, ideally a release tag
base plugin version on script version and/or make version alignment transparent, for example by an alignment table:
plugin version
script version
API version
v0.3.1
v0.3.1
v1
v0.3.0
v0.3.0
v1
Edit: on further consideration: since the plugin has exactly one job - making the scripts applicable to use with the mapping-service - it should not have its own semantic versioning and only pass through the script version.
The text was updated successfully, but these errors were encountered:
Currently multiple or all plugins rely directly on remote main branches of the scripts they are wrapping.
Building the same plugin version may therefore lead to changed plugin behaviour on script change.
Suggested changes:
Edit: on further consideration: since the plugin has exactly one job - making the scripts applicable to use with the mapping-service - it should not have its own semantic versioning and only pass through the script version.
The text was updated successfully, but these errors were encountered: