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):

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