remove-platform-version

Removes support for an older IntelliJ Platform version and cleans up obsolete code, baselines, and CI configurations.

2.0k|355|Updated Jul 25, 2016
One-click install
npx skills add https://github.com/flutter/flutter-intellij --skill remove-platform-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: remove-platform-version
Source: https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/remove-platform-version
Command: npx skills add https://github.com/flutter/flutter-intellij --skill remove-platform-version

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about remove-platform-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I drop support for an older IntelliJ Platform version in a plugin project?

Update the sinceBuild lower bound in gradle.properties, remove the version from the CI verification loop in tool/github.sh, delete its verifier baseline directory, clean up version-specific code and TODOs, and document the removal in the changelog.

How do I update the sinceBuild compatibility range for an IntelliJ plugin?

Edit gradle.properties and set sinceBuild to the new minimum build number, for example changing sinceBuild=251 to sinceBuild=252. Then run ./gradlew verifyPlugin to confirm the plugin verifies against the new range.

What files need changes when removing an Android Studio version from CI?

Remove the dropped version from the VERIFY_BOT loop in tool/github.sh and delete its baseline directory under tool/baseline/. This ensures verifyPlugin and baseline update scripts only run against supported versions.

How do I find obsolete compatibility code after dropping a platform version?

Grep the src/ directory for the removed build number or version string, such as 251 or 2025.1. Look for version-specific branches, compatibility shims, and TODO comments referencing the dropped version, then remove the dead code paths.

How do I verify an IntelliJ plugin still works after removing a platform version?

Run ./gradlew testClasses to confirm compilation, ./gradlew test for unit tests, and ./gradlew verifyPlugin to validate the plugin against the new compatibility range. All three should pass before merging.