Keeping Up to Date
The Kendo UI for Angular packages are released frequently including bug fixes and new features.
The Kendo UI for Angular packages are released together 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.
To allow updating to Minor and Patch releases, the
package.json file must references a major version range—for example,
@progress/kendo-angular-<package-name>packages must have the same version reference.
To fetch the latest compatible Minor or Patch release, run
Commit the updated
package-lock.jsonfile in the source control.
To update to the most recent versions of the Kendo UI for Angular components, use
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
npx npm-check-updates --upgrade --filter "/@progress.*/" --packageFile ./package.json
A successful run will record the updated versions in
Upgrading between major versions might require you to change the application code.
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:
ng2for Angular 2.x
ng4for Angular 4.x
ng5for Angular 5.x
ng6for Angular 6.x
ng7for Angular 7.x
ng8for Angular 8.x
ng9for Angular 9.x
ng10for Angular 10.x
ng11for Angular 11.x
ng12for Angular 12.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 @progress/kendo-angular-buttons@ng10
To generate checklists for upgrading between framework versions, use the Angular Upgrade Guide.