Hi Atlassian Developer Community,
We’re writing to let you know that Atlaskit will remove typescript@4.x support and ship exclusively for typescript@5.x (Atlaskit uses v5.9) or newer after June 15th 2026 (approximately 1 month from this notice).
Atlassian products utilise Typescript 5.x (as of 3 years ago), and none of them rely on the legacy types anymore.
Atlaskit aims to swap back to a single version of types with a minimum supported range of 5.0.
Who is affected?
Customers and partners building custom UI, or using the Connect framework, that utilise our Atlaskit components, and who build with Typescript 4 could be affected. Note that the breaking type changes may not affect all packages.
If you’re currently consuming @atlaskit packages in projects that compile with Typescript versions between 4.5 and 4.8, you could be negatively affected when you update to the next major version of these packages released after Jun 15, 2026:
{
"name": "@atlaskit/foo",
"version": "x.y.z",
"types": "dist/types/index.d.ts",
- "typesVersions": {
- ">=4.5 <4.9": {
- "*": [
- "dist/types-ts4.5/*",
- "dist/types-ts4.5/index.d.ts"
- ]
- }
- }
}
How to check if you’re affected?
Check whether you’re directly depending on and building with typescript@4.x in your project(s).
Next steps
You won’t be immediately impacted. This change will only occur when you attempt to upgrade your Atlaskit dependencies to future major versions which have dropped support for TS4.
You can continue using your existing package versions without concern. Once legacy types are removed, know that you may not be able to upgrade to the newest releases without first upgrading Typescript.
Please consider upgrading to Typescript 5 as soon as possible. This upgrade is expected to be minimal effort in most scenarios.
Typescript upgrade guidance
When upgrading to TypeScript v5+, any new errors that surface don’t indicate a regression as those issues always existed, but the previous compiler version wasn’t strict enough to detect them.
If you encounter a low number of new type errors you can choose to address them during your upgrade as a prerequisite, or if there is a significant number you can pragmatically choose to suppress (ignore) them and defer addressing them until a convenient time.
To suppress an error add a
@ts-expect-errorcomment above the affected line. e.g.
// @ts-expect-error Typescript v4 to v5 upgrade
constfoo: Foo = 'hello world'Adding an annotation such as “Typescript v4 to v5 upgrade” aids with finding them during your cleanup phase.
You may also find that previously suppressed errors aren’t needed anymore. e.g.
error TS2578: Unused '@ts-expect-error' directive. Simply remove the comments from affected lines.
You can suppress type errors without additional risk from Typescript v4, but we recommend you resolve these as soon as possible .