[Kendo CLI] migrate command ignores v19

[BRT]

 

I was following this: https://www.telerik.com/kendo-angular-ui/components/installation/migration/v18-to-v19

Gave the command: 

npx @progress/kendo-cli migrate --from=18 --to=19

And I got:

 

Why is it skipping v19? My Angular version is 19.2.x. I want to update to v19, test everything and only then migrate both Angular, Material, and Kendo to v20

Thanks in advance

[Zornitsa]

Hi,

Thank you for the provided details and resources.

Firstly, I want to clarify that the described behavior of the `kendo migrate` command has already been identified and is a known characteristic of the current implementation. The issue was consulted with a developer, and it was concluded that this is the expected behavior of the command.

To be more comprehensive, the Kendo CLI migration tool supports multiple Kendo flavors (such as KendoReact) beyond just Kendo UI for Angular. On that note, when `kendo migrate` is executed with a version flag but without specifying a particular package (like @progress/kendo-angular-dropdowns), the tool defaults to updating all detected Kendo packages in the project to their respective latest versions.

This occurs because each Kendo product has its own release-specific versions that are not applicable to packages from other product lines. Without a package context, the version parameter cannot be properly interpreted since the tool cannot determine which product's versioning scheme to apply. Therefore, when a specific package is included in the command (such as `kendo migrate @progress/kendo-angular-dropdowns --to=19`), the migration tool can then match the version to the appropriate product, and display a summary indicating the targeted update for that package and its dependencies available in the project.

With the above being said, the experienced behavior is expected, and if an assisted migration to a specific Kendo UI for Angular version is required, we recommend specifying a particular package alongside the version parameter.

We also acknowledge that there is misleading information about this command in the codemods documentation, and we sincerely apologize for any confusion this may have caused. Please be assured that we will update the documentation accordingly to clearly explain the tool's behavior and the importance of package specification when targeting specific versions.

I hope the provided information clears up the matter.

Regards,
Zornitsa
Progress Telerik