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
Sorry, automated validation of this plugin submission failed.
Here is what the validator reported:
Error: required subkey 'Darwin' not in installinstructions
Error: required subkey 'Linux' not in installinstructions
Error: required subkey 'Windows' not in installinstructions
ERROR: plugin.json metadata validation failed for lukbukkit/ftab-transform at tag '1.0.0'.
Things the validator checks:
The issue body contains a Repo URL: line pointing at a public GitHub repository.
That repository has a real (non-draft) release.
A plugin.json exists at the tag of the latest release, and is valid JSON.
plugin.json has all required fields, and type, api, platforms, and license use only supported values.
Oh great, thanks. I just was a bit confused by the different validation checks of validate_json.py / generate_plugininfo.py and the GitHub Action Vector35/plugin_actions@v1. I did perform a dry run with the GitHub release action (Validate Only) and thought that this also would include a verification of the plugin.json similar to validate_json.py.
To catch those kinds of issues in the future, I added an additional GitHub workflow to check the plugin.json based on generate_plugininfo.py: lukbukkit/ftab-transform@277b8d8 (Would that still be necessary?)
Activity
github-actions commentedon Sep 9, 2026
Sorry, automated validation of this plugin submission failed.
Here is what the validator reported:
Things the validator checks:
Repo URL:line pointing at a public GitHub repository.plugin.jsonexists at the tag of the latest release, and is valid JSON.plugin.jsonhas all required fields, andtype,api,platforms, andlicenseuse only supported values.Full log: workflow run
Once the problem is fixed (and, if needed, a new release is cut), please reopen this issue or open a new one.
psifertex commentedon Sep 9, 2026
Hmm, I think the validator is too strict there. Lemme double check and make sure nothing else requires it and i'll adjust the validator and re-open.
psifertex commentedon Sep 10, 2026
Validator is wrong re-opening.
psifertex commentedon Sep 10, 2026
Added, thanks!
lukbukkit commentedon Sep 11, 2026
Oh great, thanks. I just was a bit confused by the different validation checks of
validate_json.py/generate_plugininfo.pyand the GitHub ActionVector35/plugin_actions@v1. I did perform a dry run with the GitHub release action (Validate Only) and thought that this also would include a verification of theplugin.jsonsimilar tovalidate_json.py.To catch those kinds of issues in the future, I added an additional GitHub workflow to check the
plugin.jsonbased ongenerate_plugininfo.py: lukbukkit/ftab-transform@277b8d8 (Would that still be necessary?)