Open ponceta opened 2 hours ago
The error message is confusing because it proposes to use a '--no-validation' flag which seems to be unsupported by the package command.
This is a bug I think, the flag should exist in both commands.
But related to naming a version master
, it's dangerous IMHO for many end users. The QGIS Plugin manager will not warn at all new version of the plugin. So use this flag only if you know your users and you ask them explicitly to "reinstall the plugin later", otherwise, they will keep this plugin version for "months, years" ;-)
I'll recommend using dev
or unstable
keywords then. But in our case it is mostly to ease the package of a plugin with submodule which can be a bit tricky to test for some users.
I used qgis-plugin-ci>=2.8.6 for my test.
According to the new title :
I'll recommend using dev or unstable keywords then.
It's the same result for the QGIS plugin manager, when it's not following semantic versioning https://semver.org/
Whatever the version not following semantic versioning, QGIS plugin manager has no way to know if version=dev
is higher or lower than version 2.34.2
, so it won't propose any update to the user.
I did not find how to package (not release) a dev or master version of a plug.
The error message is confusing because it proposes to use a '--no-validation' flag which seems to be unsupported by the package command.