Repository navigation
Supported versions
TEDI (the design system developed by TEHIK) is built on modern front-end frameworks: React and Angular. Not all systems integrating TEDI can always upgrade to the latest major versions immediately due to technical debt, dependencies, or other constraints.
The version support policy is decided in the architecture decision records:
- ADR-001: React and Angular version support policy: the original policy (in Estonian)
- ADR-002: Updated Angular version support policy: supersedes ADR-001 for Angular (in Estonian)
TEDI supports different numbers of major versions per framework, because the two frameworks release at very different rates:
| Framework | Supported majors | Policy |
|---|---|---|
| React | the latest and one major older | ADR-001 |
| Angular | the three latest majors | ADR-002 |
Angular support follows Angular's own release model, which maintains the three latest major versions. On that schedule:
- support for a new Angular major is added within two months of its official release
- support for the oldest version is dropped at the same time as the new one is added
For example, when Angular 22 was released, Angular 22 support was added and Angular 19 support removed, leaving v20, v21 and v22 supported.
React support follows ADR-001: the latest stable major and one major older, maintained in parallel. React majors appear far less often than Angular's, so a two-version window gives consumers a comparable amount of migration time.
- Only critical fixes (bugs, hotfixes, accessibility improvements) are backported.
- No new features or components are introduced in the older versions.
- Documentation clearly distinguishes which updates apply only to the latest version.
The authoritative list is the peerDependencies of each library, and the Angular library's README documents the currently supported majors and the steps for adding or dropping one. As of August 2026:
| Library | Supported framework versions |
|---|---|
@tedi-design-system/react |
React 18.3.1, React 19 |
@tedi-design-system/angular |
Angular 20, 21, 22 |
Angular support is verified in CI: a compatibility job installs the built package into a fresh application for every supported Angular major.
- Clear versioning and changelogs help teams plan upgrades.
- Product owners and developers should budget for regular dependency updates to stay aligned with TEDI's support model.
- Consumers on an Angular version that Angular itself still supports are within TEDI's support window too, which was the main motivation for ADR-002.