Maven Release

Register for a Sonatype Account

First, you'll need to register for a Sonatype account at the Central Portal.

To publish under the com.google.android namespace, you'll also need to email central-support@sonatype.com with your account information to request access.

Then, generate a user token through the Sonatype website. Navigate to https://central.sonatype.com/usertoken and select Generate User Token.

Finally, add the generated token credentials to ~/.gradle/gradle.properties. (Note: these are different from the credentials used to log into your Sonatype account):

# Generated Sonatype token
sonatypeUsername=<username>
sonatypePassword=<password>

Signing Key

All release artifacts must be signed. You'll need to create an OpenPGP key pair. See Gradle's documentation on Signatory credentials for instructions.

Update ~/.gradle/gradle.properties with your new key's credentials:

signing.keyId=<key id>
signing.password=<key password>
signing.secretKeyRingFile=<secret key ring file>

Build the Android Release

Make sure JAVA_HOME is set correctly. For example:

export JAVA_HOME=/Library/Java/JavaVirtualMachines/zulu-17.jdk/Contents/Home
./build.sh -C -i -p android release

Publish to Sonatype

A Note on the Legacy Staging Service

Previously, Filament was published to Maven via OSSRH (Open Source Software Repository Hosting). In 2025, this service was sunsetted. Now, we use Sonatype's Central Publisher Portal.

The new Central Publisher Portal does not officially support Gradle. However, Sonatype provides a staging API compatibility service, which works with Filament's Gradle setup.

1. Upload to the Central Publisher Portal

To upload the artifacts, it is important to run both of these Gradle tasks together in a single command. This ensures the staging repository is created and closed automatically.

cd android
./gradlew publishToSonatype closeSonatypeStagingRepository

Troubleshooting: Manual Staging

If you ran publishToSonatype by itself, the repository will remain open and won't appear in the portal correctly. You can fix this by running our automation script, which uses the sonatypeUsername and sonatypePassword from your ~/.gradle/gradle.properties file:

python3 build/common/close-sonatype-staging-repository.py

2. Publish the Release on Sonatype

Once the upload is successful, you must manually trigger the final release. Navigate to Maven Central Repository Deployments.

Here, you should see a new deployment with a Validated status and all your artifacts listed. Click the Publish button to publish the artifacts. It typically takes around 5 minutes after clicking Publish for the artifacts to go live.