Resolves https://github.com/material-components/material-components-android/pull/1809 GIT_ORIGIN_REV_ID=8be49f3880de2691d85faabcde809e878f83b498 PiperOrigin-RevId: 340224359
3.2 KiB
Using a Snapshot Version of the Library
If you would like to depend on the cutting edge version of the MDC-Android library, you can use the snapshot versions that are published daily via GitHub Packages.
To do so, you need to
create a GitHub access token
with the read:packages scope, and add the following to your build.gradle
Maven repositories, replacing <github_username> and <github_access_token>
with your credentials:
maven {
name = "MaterialSnapshots"
url = uri("https://maven.pkg.github.com/material-components/material-components-android")
credentials {
username = "<github_username>"
password = "<github_access_token>"
}
}
Then you can use a snapshot version by adding a
com.google.android.material:material:<version>-SNAPSHOT dependency as per
usual (see latest release
here).
This will fetch the latest snapshot version, which your Gradle build won't
cache. If you build after a new version has been published, that version will be
used.
See the offical doc on Configuring Gradle for use with GitHub Packages for additional information.
If you prefer to depend on a specific snapshot version, you can add
com.google.android.material:material:<version>-<uniqueversion>, where
<uniqueversion> is a combination of the date, a timestamp, and a counter (see
all versions
here).
You can also find the list of versions through the GraphQL explorer with the following query:
{
node(id: "MDE0OlBhY2thZ2VWZXJzaW9uMjMyNDc2OQ==") {
... on PackageVersion {
id
version
files(last: 12, orderBy: {field: CREATED_AT, direction: ASC}) {
nodes {
name
}
}
}
}
}
Alternatively, you could use JitPack to generate library releases based on specific commits.