Progress tracker

A progress tracker displays the steps and progress through a journey.

11.4.1

Patch Changes

  • Updated dependencies

11.4.0

Minor Changes

Patch Changes

  • Updated dependencies

11.3.2

Patch Changes

11.3.1

Patch Changes

  • Use @atlassian/testing-library exclusively in unit tests.

11.3.0

Minor Changes

  • d82e6f76528ab, (opens new window) - Add direct subpath package exports as part of the linking-platform, search, media, and design-system barrel-removal (de-barrel) migration.

    These packages now expose their individual modules via explicit package.json exports subpaths so that consumers can import directly from the leaf module (e.g. @atlaskit/pkg/thing) instead of the package barrel/index. This adds new public entry points without changing or removing any existing exports, so it is a backwards-compatible additive change.

    No runtime behaviour changes; this is an API-surface (entry-point) addition to support tree-shaking and to unblock removal of the barrel index files.

Patch Changes

  • Updated dependencies

11.2.3

Patch Changes

  • Updated dependencies

11.2.2

Patch Changes

  • Updated dependencies

11.2.1

Patch Changes

  • Updated dependencies

11.2.0

Minor Changes

Patch Changes

  • Updated dependencies

11.1.0

Minor Changes

  • cd097a2111788, (opens new window) - Republish packages depending on @atlaskit/react-compiler-gating so their published dependency reference is updated to the renamed @atlaskit/react-compiler-gating scope.

    The earlier rename of @atlassian/react-compiler-gating to @atlaskit/react-compiler-gating only bumped the renamed package itself, so dependent packages were never republished and their published versions still referenced the old @atlassian/react-compiler-gating name, which is not available in the public npm registry. This minor bump republishes all affected packages with the corrected dependency.

Patch Changes

  • Updated dependencies

11.0.1

Patch Changes

11.0.0

Major Changes

  • f2dc9097319f0, (opens new window) - ### Dropped support for legacy Typescript 4 types. Typescript 5 is now the new minimum.

    Removes the typesVersions property and dist/types-ts4.5 directory from the dist.

    Types are now exclusively via the "types": "dist/types/index.d.ts" property.

    - "typesVersions": { - ">=4.5 <4.9": { - "*": [ - "dist/types-ts4.5/*", - "dist/types-ts4.5/index.d.ts" - ] - } - },

Patch Changes

  • Updated dependencies

10.5.7

Patch Changes

  • Updated dependencies

10.5.6

Patch Changes

  • Updated dependencies

10.5.5

Patch Changes

10.5.4

Patch Changes

10.5.3

Patch Changes

10.5.2

Patch Changes

10.5.1

Patch Changes

  • Updated dependencies

10.5.0

Minor Changes

10.4.3

Patch Changes

  • Updated dependencies

10.4.2

Patch Changes

  • Updated dependencies

10.4.1

Patch Changes

  • Updated dependencies

10.4.0

Minor Changes

10.3.12

Patch Changes

  • Updated dependencies

10.3.11

Patch Changes

  • Updated dependencies

10.3.10

Patch Changes

  • Updated dependencies

10.3.9

Patch Changes

  • Updated dependencies

10.3.8

Patch Changes

  • Updated dependencies

10.3.7

Patch Changes

  • Updated dependencies

10.3.6

Patch Changes

  • Updated dependencies

10.3.5

Patch Changes

  • Updated dependencies

10.3.4

Patch Changes

  • Updated dependencies

10.3.3

Patch Changes

  • Updated dependencies

10.3.2

Patch Changes

  • Updated dependencies

10.3.1

Patch Changes

  • Updated dependencies

10.3.0

Minor Changes

10.2.2

Patch Changes

  • Updated dependencies

10.2.1

Patch Changes

  • Updated dependencies

10.2.0

Minor Changes

10.1.3

Patch Changes

  • Updated dependencies

10.1.2

Patch Changes

  • Updated dependencies

10.1.1

Patch Changes

10.1.0

Minor Changes

Patch Changes

  • Updated dependencies

10.0.4

Patch Changes

10.0.3

Patch Changes

10.0.2

Patch Changes

  • Updated dependencies

10.0.1

Patch Changes

10.0.0

Major Changes

Patch Changes

  • Updated dependencies

9.4.0

Minor Changes

Patch Changes

  • Updated dependencies

9.3.3

Patch Changes

  • Updated dependencies

9.3.2

Patch Changes

  • Updated dependencies

9.3.1

Patch Changes

  • Updated dependencies

9.3.0

Minor Changes

Patch Changes

  • Updated dependencies

9.2.0

Minor Changes

9.1.0

Minor Changes

9.0.3

Patch Changes

9.0.2

Patch Changes

  • Updated dependencies

9.0.1

Patch Changes

9.0.0

Major Changes

  • #171836, (opens new window) 30eff06f3753e, (opens new window) - Migrated from @emotion/react to @compiled/react in order to improve performance, align with the rest of the Atlaskit techstack, and support React 18 Streaming SSR.

    Please note, in order to use this version of @atlaskit/progress-tracker, you will need to ensure that your bundler is configured to handle .css imports correctly. Most bundlers come with built-in support for .css imports, so you may not need to do anything. If you are using a different bundler, please refer to the documentation for that bundler to understand how to handle .css imports.

    For more information on the migration, please refer to RFC-73 Migrating our components to Compiled CSS-in-JS, (opens new window).

8.11.1

Patch Changes

  • Updated dependencies

8.11.0

Minor Changes

8.10.3

Patch Changes

8.10.2

Patch Changes

8.10.1

Patch Changes

  • Updated dependencies

8.10.0

Minor Changes

8.9.4

Patch Changes

  • Updated dependencies

8.9.3

Patch Changes

8.9.2

Patch Changes

  • Updated dependencies

8.9.1

Patch Changes

8.9.0

Minor Changes

8.8.2

Patch Changes

8.8.1

Patch Changes

  • Updated dependencies

8.8.0

Minor Changes

  • #127511, (opens new window) db30e29344013, (opens new window) - Widening range of react and react-dom peer dependencies from ^16.8.0 || ^17.0.0 || ~18.2.0 to the wider range of ``^16.8.0 || ^17.0.0 || ^18.0.0` (where applicable).

    This change has been done to enable usage of react@18.3 as well as to have a consistent peer dependency range for react and react-dom for /platform packages.

Patch Changes

  • Updated dependencies

8.7.6

Patch Changes

  • Updated dependencies

8.7.5

Patch Changes

8.7.4

Patch Changes

  • Updated dependencies

8.7.3

Patch Changes

  • Updated dependencies

8.7.2

Patch Changes

  • Updated dependencies

8.7.1

Patch Changes

  • Updated dependencies

8.7.0

Minor Changes

Patch Changes

  • Updated dependencies

8.6.3

Patch Changes

8.6.2

Patch Changes

  • Updated dependencies

8.6.1

Patch Changes

8.6.0

Minor Changes

8.5.11

Patch Changes

  • Updated dependencies

8.5.10

Patch Changes

8.5.9

Patch Changes

  • Updated dependencies

8.5.8

Patch Changes

  • Updated dependencies

8.5.7

Patch Changes

  • Updated dependencies

8.5.6

Patch Changes

  • Updated dependencies

8.5.5

Patch Changes

8.5.4

Patch Changes

  • Updated dependencies

8.5.3

Patch Changes

8.5.2

Patch Changes

8.5.1

Patch Changes

8.5.0

Minor Changes

Patch Changes

  • Updated dependencies

8.4.10

Patch Changes

8.4.9

Patch Changes

8.4.8

Patch Changes

8.4.7

Patch Changes

8.4.6

Patch Changes

  • Updated dependencies

8.4.5

Patch Changes

8.4.4

Patch Changes

8.4.3

Patch Changes

8.4.2

Patch Changes

  • Updated dependencies

8.4.1

Patch Changes

  • Updated dependencies

8.4.0

Minor Changes

8.3.4

Patch Changes

  • Updated dependencies

8.3.3

Patch Changes

8.3.2

Patch Changes

8.3.1

Patch Changes

8.3.0

Minor Changes

Patch Changes

  • Updated dependencies

8.2.5

Patch Changes

8.2.4

Patch Changes

  • Updated dependencies

8.2.3

Patch Changes

8.2.2

Patch Changes

  • Updated dependencies

8.2.1

Patch Changes

  • Updated dependencies

8.2.0

Minor Changes

  • #19019, (opens new window) 4e96270c06e, (opens new window) - [ux] Instrumented progress-tracker with the new theming package, @atlaskit/tokens.

    New tokens will be visible only in applications configured to use the new Tokens API (currently in alpha). These changes are intended to be interoperable with the legacy theme implementation. Legacy dark mode users should expect no visual or breaking changes.

Patch Changes

  • Updated dependencies

8.1.0

Minor Changes

8.0.4

Patch Changes

  • Updated dependencies

8.0.3

Patch Changes

8.0.2

Patch Changes

8.0.1

Patch Changes

8.0.0

Major Changes

Patch Changes

  • Updated dependencies

7.0.6

Patch Changes

7.0.5

Patch Changes

7.0.4

Patch Changes

  • Updated dependencies

7.0.3

Patch Changes

7.0.2

Patch Changes

7.0.1

Patch Changes

7.0.0

Major Changes

Patch Changes

  • Updated dependencies

6.1.8

Patch Changes

6.1.7

Patch Changes

6.1.6

Patch Changes

6.1.5

Patch Changes

6.1.4

Patch Changes

6.1.3

Patch Changes

6.1.2

Patch Changes

6.1.1

Patch Changes

6.1.0

Minor Changes

6.0.8

Patch Changes

  • [patch]4432d729b7, (opens new window):

    @atlaskit/progress-tracker has been converted to Typescript. Typescript consumers will now get static type safety. Flow types are no longer provided. No API or behavioural changes.

6.0.7

Patch Changes

  • [patch]097b696613, (opens new window):

    Components now depend on TS 3.6 internally, in order to fix an issue with TS resolving non-relative imports as relative imports

6.0.6

Patch Changes

6.0.5

Patch Changes

6.0.4

Patch Changes

6.0.3

Patch Changes

6.0.2

Patch Changes

6.0.1

6.0.0

  • [major]7c17b35107, (opens new window):
    • Updates react and react-dom peer dependencies to react@^16.8.0 and react-dom@^16.8.0. To use this package, please ensure you use at least this version of react and react-dom.

5.0.2

5.0.1

5.0.0

  • [major]76299208e6, (opens new window):

    • Drop ES5 from all the flow modules

    Dropping CJS support in all @atlaskit packages

    As a breaking change, all @atlaskit packages will be dropping cjs distributions and will only distribute esm. This means all distributed code will be transpiled, but will still contain import and export declarations.

    The major reason for doing this is to allow us to support multiple entry points in packages, e.g:

    import colors from `@atlaskit/theme/colors`;

    Previously this was sort of possible for consumers by doing something like:

    import colors from `@atlaskit/theme/dist/esm/colors`;

    This has a couple of issues. 1, it treats the file system as API making internal refactors harder, we have to worry about how consumers might be using things that aren't actually supposed to be used. 2. We are unable to do this internally in @atlaskit packages. This leads to lots of packages bundling all of theme, just to use a single color, especially in situations where tree shaking fails.

    To support being able to use multiple entrypoints internally, we unfortunately cannot have multiple distributions as they would need to have very different imports from of their own internal dependencies.

    ES Modules are widely supported by all modern bundlers and can be worked around in node environments.

    We may choose to revisit this solution in the future if we find any unintended condequences, but we see this as a pretty sane path forward which should lead to some major bundle size decreases, saner API's and simpler package architecture.

    Please reach out to #fabric-build (if in Atlassian) or create an issue in Design System Support, (opens new window) (for external) if you have any questions or queries about this.

4.0.10

4.0.9

4.0.8

4.0.7

4.0.5

4.0.4

4.0.3

4.0.2

4.0.1

4.0.0

3.1.2

3.1.1

3.1.0

3.0.1

3.0.0

2.0.3

2.0.2

2.0.0

1.3.1

1.3.0

1.2.2

1.2.1

1.2.0

1.1.0

1.0.2

0.2.0

Was this page helpful?
We use this feedback to improve our documentation.
© 2026 AtlassianTrademark, (opens new window)Privacy, (opens new window)License