# Automate MIN\_SDK\_VERSION bump (`aspiring_hypotenuse_ior/automate-min-sdk-version-bump`) Actor

Automate MIN\_SDK\_VERSION bump via release pipeline + AI-based SDK-breaking-change detection, a repetitive task that could be automated with a tool.

- **URL**: https://apify.com/aspiring\_hypotenuse\_ior/automate-min-sdk-version-bump.md
- **Developed by:** [Lore Nest](https://apify.com/aspiring_hypotenuse_ior) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Automate MIN\_SDK\_VERSION bump

Automate MIN\_SDK\_VERSION bump via release pipeline + AI-based SDK-breaking-change detection, a repetitive task that could be automated with a tool.

This Actor keeps your Android project's `minSdkVersion` up to date by detecting SDK-related breaking changes from change descriptions and computing the next required version. It accepts a current version, a list of textual change notes, and an optional bump amount, then returns the new minimum SDK value along with the justification. Use it as a lightweight gate inside a release pipeline so that every version bump is traceable to a concrete signal rather than a manual checklist.

### Use Cases

- **Release pipeline gate for Android apps** — Drop the Actor into a CI/CD workflow so that whenever a release is prepared, the new `minSdkVersion` is computed automatically and attached to the build manifest before publication.
- **Keyword-driven breaking-change triage** — Feed it commit messages, pull request titles, or changelog entries containing terms like `SDK`, `API level`, `incompatible`, `requires`, or `bump` to flag whether a minimum SDK increase is warranted.
- **Version-mention parsing in change logs** — Pass changelog lines that mention numeric versions (e.g., "updated to API 34") and let the Actor detect when a referenced version number is higher than the current minimum, triggering a justified bump.
- **Configurable increment size for staged rollouts** — Supply a custom `bump_amount` (default `1`) to support projects that move `minSdkVersion` by more than one level per release, such as when skipping unsupported API ranges.
- **Safe defaulting for incomplete inputs** — Rely on the Actor's fallback behavior to default the current version to `21`, extract a numeric version from messy strings via regex, and ignore malformed change entries instead of failing the pipeline.

### How It Works

The Actor's `run` function first normalizes the `current_min_sdk_version` input, falling back to `21` when the value is missing or unparsable, including extracting digits from mixed strings. It then iterates over each entry in the `changes` list, scanning for breaking-change keywords such as `minSdkVersion`, `SDK`, `breaking change`, or `requires`; the first match flips `should_bump` to `True` and records the offending change as the reason. If no keyword hits, the function additionally parses embedded integers from each change and flags an increase whenever a number exceeds the current version and the surrounding text mentions `sdk`, `version`, or `api`. Finally, the computed bump amount is added to the current version (when warranted) to produce the new minimum SDK value returned to the caller.

### Usage on Apify

Run it directly from the Apify Console ("Start"/"Try for free"), or call it via the API:

```
POST https://api.apify.com/v2/acts/automate-min-sdk-version-bump/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>
Content-Type: application/json

{}
```

### Pricing

Pay-per-event, billed automatically by Apify -- no separate account or payment step:

- Actor start: $0.00005 per GB of memory (minimum one event per run)
- Result: $0.005 per item returned -- this is the primary, usage-based charge

Also independently available at $0.0100 USDC (Base) per call via the x402 payment protocol (`POST /tools/automate-min-sdk-version-bump`) for callers outside the Apify platform.

### Example output

Real output captured from this tool's own build-time smoke test (input above):

```json
{
  "new_min_sdk_version": "21",
  "should_bump": false,
  "reason": "No breaking changes detected"
}
```

# Actor input Schema

## `bump_amount` (type: `integer`):

Real parameter read as payload\['bump\_amount'] in this tool's own generated code.

## `changes` (type: `string`):

Real parameter read as payload\['changes'] in this tool's own generated code.

## `current_min_sdk_version` (type: `string`):

Real parameter read as payload\['current\_min\_sdk\_version'] in this tool's own generated code.

## Actor input object example

```json
{
  "bump_amount": 1
}
```

# Actor output Schema

## `output` (type: `string`):

Real dataset items pushed via Actor.push\_data() in src/main.py -- each item is exactly the dict this tool's own run() returns. This tool's own real, build-time-captured output had these top-level fields: new\_min\_sdk\_version, reason, should\_bump.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("aspiring_hypotenuse_ior/automate-min-sdk-version-bump").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("aspiring_hypotenuse_ior/automate-min-sdk-version-bump").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call aspiring_hypotenuse_ior/automate-min-sdk-version-bump --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,aspiring_hypotenuse_ior/automate-min-sdk-version-bump"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/kgPOVPgihmaBqgQbo/builds/PWzs3SiduCBODlzUA/openapi.json