Does the App follow semantic versioning?

Workflow Script app

Workflow Script app version: 1.9.0

https://github.com/nextcloud/workflow_script/commit/44f73abcda15d2cc0b6e757695002efae61c0afa seems to introduce several breaking changes.

E.g. in Launcher.php the signature of OCA\WorkflowScript\BackgroundJobs\Launcher's constructor changes from

public function __construct(LoggerInterface $logger, ITempManager $tempManager, IRootFolder $rootFolder)

to

public function __construct(ITimeFactory $time, LoggerInterface $logger)

Similarly affected is OCA\WorkflowScript\Operation and more subtly OCA\WorkflowScript\Listener\RegisterFlowOperationsListener where only the interface of the parameter changes.

Do these changes not violate the backwards-compatibility requirement, that is implied by the same major version?

Hence, should version 1.9.0 not have been 2.0.0 instead?

The whole idea of semantic versioning is to avoid code breaks on dependencies. According to the (developer documentation)[https://nextcloudappstore.readthedocs.io/en/latest/developer.html#info-xml], version numbers must follow semantic versioning.

Esamina le modifiche al costruttore in Launcher.php e le classi referenziate Operation e RegisterFlowOperationsListener nel commit 44f73abcda15d2cc0b6e757695002efae61c0afa. Confronta tali modifiche con le linee guida sul versionamento semantico collegate nell’issue e con i metadati di release dell’app; il lavoro è completato quando viene registrato se 1.9.0 è compatibile con la policy indicata e quale azione di versionamento o documentazione ne consegue.