Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make plugin versions more stable and document version alignment #5

Open
GGoetzelmann opened this issue Jan 21, 2025 · 0 comments
Open

Comments

@GGoetzelmann
Copy link

GGoetzelmann commented Jan 21, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant