<h1>How to deal with the pace of changing the Android SDK?</h1>
In the modern day of mobile development, where everything is modular, 
and the updates is shipped rapidly, you can easily be lost in the 
process of manual updates of your dependencies. While there exists 
solutions like [Renovate] and [Dependabot], the best application of
these solutions are to maintain the external dependencies and libraries.
But how can we make sure, that if Android compileSDK and targetSDK are 
up-to-date, if the application logic is not shifting that often, as 
the SDK&#39;-s? Well, today we would like to share our journey with this, 
welcome aboard!
<h2>Determining the source of truth for Android SDK versions</h2>
Upon deep investigation and the <a href="https://android.googlesource.com/platform/tools/base/+/master/sdklib/src/main/java/com/android/sdklib/SdkManager.java">Android source code</a>, our team have found,
that SDKManager is fetching data from <a href="https://dl.google.com/android/repository/repository2-1.xml">https://dl.google.com/android/repository/repository2-1.xml</a>.
This XML contains a lot of information, but the most important to us is &quot;Android SDK Platform XX&quot;, where XX -
is the Android SDK version. Exactly this information we will need to determine 
if our application is behind the official SDK&#39;s provided by Android development team.
For ease of use, there&#39;s a docker image already with necessary steps done: ghcr.io/fallenangel97/android-fetcher:master
<h2>Process of bumping the SDK&#39;-s in the application code</h2>
Now, when we know, where to look at the most up-to-date Android SDK version, 
we need to find a way how to specify the logic to update necessary API&#39;s. 
In order to do that, we will create <code>scripts</code> folder inside the root folder of the 
necessary Android application. Now, whenever the docker image will detect versions of Android SDK, 
it will send them to that folder as an arguments, so that we can read them and 
construct the logic for updating necessary files. 
Example of such script can look like this:
<pre><code class="hljs language-bash">#!/bin/sh
# filename: &lt;project-root&gt;/scripts/bump-android-version.sh

base_path=$(dirname -- &quot;$0&quot;)
node $base_path/js/bump-version.js $1
</code></pre><pre><code class="hljs language-javascript">const { execSync } = require(&#x27;child_process&#x27;);
const { readFileSync, writeFileSync } = require(&#x27;fs&#x27;);
const path = require(&#x27;path&#x27;);

const [,,remoteVersions] = process.argv;

const parsedVersions = JSON.parse(remoteVersions);
const latestAndroidVersion = Math.max(...parsedVersions);

const fileContents = readFileSync(path.join(__dirname,&#x27;../../app/build.gradle&#x27;)).toString();

const targetSdkRegex = /targetSdkVersion ([0-9]+)/;
const compileSdkRegex = /compileSdkVersion ([0-9]+)/;

const match = targetSdkRegex.exec(fileContents);

if (match.length &gt; 0) {
 const [,version] = match;

 if (parseInt(latestAndroidVersion) &gt; parseInt(version)) {
 console.log(&#x27;Replacing the android version...&#x27;);
 const newText = fileContents
 .replace(targetSdkRegex, &quot;targetSdkVersion &quot; + latestAndroidVersion)
 .replace(compileSdkRegex, &quot;compileSdkVersion &quot; + latestAndroidVersion);
 writeFileSync(path.join(__dirname, &#x27;../../app/build.gradle&#x27;), newText);
 execSync(&#x27;git add .&#x27;);
 execSync(`git checkout -b bump-android-${latestAndroidVersion}`);
 execSync(`git commit -m &#x27;Bumped targetSdkVersion and compileSdkVersion to ${latestAndroidVersion}&#x27;`);
 execSync(`git push -o merge_request.create -o merge_request.merge_when_pipeline_succeeds origin HEAD`);
 } else {
 console.log(&#x27;The version is up to date, exiting&#x27;);
 }
}
</code></pre>Of course, you should adjust the scripts up to your requirements.
<h2>Putting everything together as a periodic task</h2>
We&#39;ll use a wonderful <a href="https://crazymax.dev/swarm-cronjob/">docker-cron project</a> in order to connect our pieces together. 
Let&#39;s run our process for bumping Android version every 8 hours, so we can define the logic for swarm-cronjob like this:
<pre><code class="hljs language-yml">version: &quot;3.8&quot;

services:
 android_sdk_bumper:
 image: &quot;ghcr.io/fallenangel97/android-fetcher:master&quot;
 healthcheck:
 disable: true
 environment:
 - REPOSITORIES=&quot;&lt;path-to-your-git-repo&gt;&quot;
 volumes:
 - &quot;/root/.ssh:/root/.ssh&quot;
 deploy:
 mode: replicated
 replicas: 0
 labels:
 - &quot;swarm.cronjob.enable=true&quot;
 - &quot;swarm.cronjob.schedule=0 */8 * * *&quot;
 restart_policy:
 condition: none
</code></pre>Make sure, that you have generated SSH keys and added them in your Git 
service in order for the &quot;git clone&quot; to work properly, otherwise it might fail
You are welcome to create a PR for the project here: <a href="https://github.com/FallenAngel97/android-list-fetcher">https://github.com/FallenAngel97/android-list-fetcher</a>
Photo by <a href="https://unsplash.com/@jxk?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Jan Kopřiva</a> on <a href="https://unsplash.com/photos/red-and-black-metal-tool-aHSejd0UGEo?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash">Unsplash</a>