New to Kendo UI for Angular? Start a free 30-day trial

Keeping Up to Date

The Kendo UI for Angular packages are released frequently including bug fixes and new features.

Starting with Kendo UI for Angular v19.0.0, some component packages now provide codemods to help you migrate between major versions. For more details, check out Migrating Your Code.

Semantic Versioning

The Kendo UI for Angular packages are released together (all @progress/kendo-angular-* packages have the same version) and their version numbers follow the rules of Semantic Versioning:

A major version bump (X.y.z) signals a breaking change in the API. You might need to update application code or dependencies.
A minor version bump (x.Y.z) signals the addition of new features. Existing code will continue to work but new features may require additional setup.
A patch version bump (x.y.Z) indicates a bug-fix release. Typically, patches do not require changes to application code.

To see the list of changes for each release, see the detailed changelog.

Prior to version 11, the @progress/kendo-angular-<package-name> packages used independent versioning and shipped individual changelogs. See https://github.com/telerik/kendo-angular/issues/3859 for details about this change.

Updating to Compatible Releases

To allow updating to Minor and Patch releases, the package.json file must references a major version range—for example, "@progress/kendo-angular-grid": "^3.0.0".

All @progress/kendo-angular-<package-name> packages must have the same version reference.

To fetch the latest compatible Minor or Patch release, run npm update.

Commit the updated package-lock.json file in the source control.

Updating to Latest Versions

To update to the most recent versions of the Kendo UI for Angular components, use npm-check-updates.

To upgrade all Progress packages, run:

npx npm-check-updates --upgrade --filter "/@progress.*/"

To upgrade only Kendo UI for Angular packages, run:

npx npm-check-updates --upgrade --filter "/@progress/kendo-angular.*/"

In some cases, you may have to specify the location of the package.json file:

npx npm-check-updates --upgrade --filter "/@progress.*/" --packageFile ./package.json

A successful run will record the updated versions in package.json and package-lock.json.

Upgrading between major versions might require you to change the application code.

For more details, refer to the Changelogs and Rendering Changes documentation.

Updating to Unsupported Releases

The latest versions of the packages are compatible with the Active and LTS versions of Angular. To update to the most recent versions of the Kendo UI for Angular components that are compatible with a legacy version of Angular, use the respective distribution tags:

ng2 for Angular 2.x
ng4 for Angular 4.x
ng5 for Angular 5.x
ng6 for Angular 6.x
ng7 for Angular 7.x
ng8 for Angular 8.x
ng9 for Angular 9.x
ng10 for Angular 10.x
ng11 for Angular 11.x
ng12 for Angular 12.x
ng13 for Angular 13.x
ng14 for Angular 14.x
ng15 for Angular 15.x

Apply the distribution tag to all packages to obtain the correct versions.

For example, to update to the latest version of the Buttons package that is compatible with Angular 10.x, run:

npm install --save @progress/kendo-angular-buttons@ng10

To add a package to an existing Angular 10.x project, use ng add:

ng add @progress/kendo-angular-buttons@ng10

Updating Angular

To generate checklists for upgrading between framework versions, use the Angular Upgrade Guide.