What problem does it solve?
Dropping support for an older IntelliJ Platform or Android Studio version requires coordinated edits across build files, CI scripts, verifier baselines, compatibility code, and changelogs, and missing any of them leaves stale configuration or dead code behind.
Core Features & Use Cases
- Compatibility Range Updates: Raises the
sinceBuild lower bound in gradle.properties and removes the dropped version from the CI verification loop in tool/github.sh.
- Obsolete Code Cleanup: Removes verifier baseline directories, version-specific branches, workarounds, and TODOs tied to the dropped build number.
- Documentation & Validation: Updates the changelog, checks repository issues for tracked cleanup tasks, and verifies the result with
testClasses, test, and verifyPlugin Gradle tasks.
- Use Case: When the Flutter IntelliJ plugin drops support for platform 2025.1 (build 251) and raises the minimum to 2025.2 (build 252), this Skill walks through every file and check that must change.
Quick Start
Remove support for IntelliJ platform version 2025.1 and raise the minimum supported build to 252.