verify-eap-compatibility

Name: verify-eap-compatibility
Availability: InStock
Author: Flutter

Verifies IntelliJ plugin compatibility against latest EAP platform builds using Gradle tasks.

2.0k|355|Updated Jul 25, 2016

Search Tags:#compatibility #plugin #gradle #jetbrains #intellij #eap #verifyplugin

Ready to run

npx skills add https://github.com/flutter/flutter-intellij --skill verify-eap-compatibility

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verify-eap-compatibility
Source: https://github.com/flutter/flutter-intellij/tree/main/.agents/skills/verify-eap-compatibility
Command: npx skills add https://github.com/flutter/flutter-intellij --skill verify-eap-compatibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

IntelliJ Platform EAP releases frequently introduce breaking API changes, and plugin authors must proactively detect compilation errors, binary incompatibilities, and incorrect version bounds before users on new IDE builds are affected.

Core Features & Use Cases

EAP Targeting: Temporarily updates gradle.properties to compile against the latest IntelliJ Platform EAP version.
Automated Verification: Runs ./gradlew testClasses, ./gradlew verifyPlugin, and ./gradlew test to catch compilation errors, binary incompatibilities, and functional regressions.
Version Bounds Review: Checks plugin.xml <idea-version> attributes to ensure until-build is open-ended or correctly set.
Use Case: When JetBrains publishes a new IntelliJ EAP build, run this workflow to confirm the Flutter plugin still compiles and passes verification, then receive a summary of required fixes and a suggested commit message.

Quick Start

Verify the plugin against the latest IntelliJ EAP build and report any compatibility issues or required fixes.

Frequently Asked Questions about verify-eap-compatibility

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

FAQPage Schema

How do I verify IntelliJ plugin compatibility with EAP builds?▼

Update gradle.properties to target the EAP version, then run ./gradlew testClasses to compile, ./gradlew verifyPlugin to detect binary incompatibilities, and ./gradlew test to check for functional regressions.

How to check plugin.xml version bounds for a new IntelliJ release?▼

Review the <idea-version since-build="..." until-build="..."/> element in plugin.xml. Ensure until-build is open-ended or set appropriately for the new platform version so the plugin remains installable.

What does the Gradle verifyPlugin task check?▼

The verifyPlugin task checks the plugin for binary incompatibilities and broken API usages against the targeted IntelliJ Platform version, surfacing problems introduced by platform changes in new releases.

Why does my IntelliJ plugin fail to compile against an EAP build?▼

EAP builds often change or remove platform APIs before stable release. Compilation failures indicate the plugin references deprecated or altered APIs that must be updated to match the new platform version.

Should I commit EAP compatibility fixes automatically?▼

No. The workflow explicitly avoids committing or pushing changes. It summarizes required fixes, states where to test functionality in the IDE, and provides a suggested commit message for manual review.