Feature Description
In #686 we added a new GitHub workflow for deploying modules as standalone plugins (see: #638). This includes a workflow_dispatch trigger to do manual releases of a standalone plugin. The current manual workflow supports two text inputs, one for the plugin slug and one for the version number (see screenshot below)

While this works, it creates an opportunity for human error if someone mistypes the slug or the version. I would suggest two changes:
- Replace the text input for the slug with a dropdown to select the specific modules we support. This can use the
choice input type for the workflow (see docs).
- Remove the input for setting the version number and instead use the version number from the
plugins.json file. This means we would need to make sure that file is updated with the correct version number before a manual plugin release is completed, but would be more consistent, as the version number will match the version included in the built plugin.
Feature Description
In #686 we added a new GitHub workflow for deploying modules as standalone plugins (see: #638). This includes a
workflow_dispatchtrigger to do manual releases of a standalone plugin. The current manual workflow supports two text inputs, one for the plugin slug and one for the version number (see screenshot below)While this works, it creates an opportunity for human error if someone mistypes the slug or the version. I would suggest two changes:
choiceinput type for the workflow (see docs).plugins.jsonfile. This means we would need to make sure that file is updated with the correct version number before a manual plugin release is completed, but would be more consistent, as the version number will match the version included in the built plugin.