Release Process

Generate the maven artifacts that most users need

• Test the jar against Anki-Android
• Pull the latest version of main
• Update gradle.properties: increment version number
• Obtain changelog: compare from last tag
• Commit the change to gradle.properties
  • Title: release: x.x.x
  • body: changelog
• Pull Request and merge into main [sample]
• Add and push tag (x.x.x)
• Pre-publish to OSS Sonatype
  • Run https://github.com/david-allison-1/Anki-Android-Backend/actions/workflows/publish_library.yml
  • Run https://github.com/david-allison-1/Anki-Android-Backend/actions/workflows/publish_testing.yml
  • If either fails, resolve the issue and start again with a new version number
• Login to OSS Sonatype
  • Currently David Allison and Mike Hardy have the credentials to do this
  • Staging Repositories
• Close both repositories
• Release both repositories
  • Automatically Drop
• Update Anki-Android's dependency on the backend
  • Currently in build.gradle, as variable ext.ankidroid_backend_version

Generate the Apple Silicon CPU architecture dylib

• Run the commands to generate it, from the root of Anki-Android-Backend clone:

# install all requirements, make sure environment is good
./tools/doctor.sh
# make sure we build things clean
\rm -fr rslib-bridge/target
./gradlew clean
# get the buildinfo from rslib
./tools/get-buildinfo.sh  # may require `brew install bazelisk` first
# do the build
./gradlew assembleRelease -DtestBuildType=release  # this may not be necessary? have not tested without running it
cd rslib-bridge
cross build --release --features no-android --verbose --target aarch64-apple-darwin
# open up a finder window with dylib named correctly, ready to go for drag-and-drop on the releases page
cd target/aarch64-apple-darwin/release
mv librsdroid.dylib librsdroid-arm64.dylib
open .

• Open the github tag for the latest build
• Hit the pencil icon to edit the tag
• Drag the librsdroid-arm64.dylib file from the Finder window to the file drop area
• Save the edits and now Apple Silicon users may successfully run robolectric tests