Jetpack libraries ship separately from the Android OS, so updates to the
libraries can happen independently and more frequently.
The libraries follow strict semantic versioning for binary compatibility with an added inter-version sequence of pre-release revisions.
A version string (like 1.0.1-beta02) contains three numbers representing major, minor, and bugfix levels.
Pre-release versions also have a suffix that specifies the pre-release stage
(alpha, beta, release candidate) and revision number (01, 02, and so on).
Please note that androidx libraries are encouraged, but not required, to preserve source compatibility across minor versions. The reason being a major version update would force all artifacts that depend on the previous major version to be explicitly migrated, which would disrupt the workflow of developers.
Every version of a library moves through three pre-release stages on its way to
becoming a stable release. The criteria for each pre-release stage is:
Alpha releases are functionally stable, but may not be feature-complete.
While a release is in alpha, APIs may be added, removed, or changed.
Beta releases are functionally stable and have a feature-complete API surface.
They are ready for production use but may contain bugs.
A beta release cannot use experimental compiler features
(such as @UseExperimental).
Dependencies on other libraries must be beta, rc, or stable
versions. No alpha dependencies are allowed.
Release Candidate (RC)
A release candidate is a prospective stable release.
It may contain critical last-minute fixes.
Its API surface is final.
Dependencies on other libraries must be rc or stable versions only.
A library can have multiple versions at the same time. Each version has a
different release stage. For example, while the stable release of
androidx.activity could be 1.0.0, there might also be a 1.1.0-beta02
release as well as a 2.0.0-alpha01 release.
Use this page to learn of the latest updates to the libraries.
Use the table below to view the most recent stable and preview versions of every
AndroidX library. The links on each row take you to the library's release notes.
In the release notes you'll find:
The chronological history of all the releases.
A code snippet with the default Gradle dependency declarations to use the artifacts.
Links to the Kotlin and Java reference pages for the packages in each artifact.
Some AndroidX libraries, like camera, have multiple artifacts that are
maintained separately. These libraries are marked with an asterisk (*). See the
release notes to view the version updates for all of the artifacts.