Gap Hunter Labs
Work with me

Work with me

Plugin updates for new IDE versions

For teams that maintain a JetBrains plugin and need it compatible with each new IntelliJ Platform release. A fixed scope and a fixed price, delivered as a pull request with the Plugin Verifier report for every version you support.

Ask for a quote Use the contact page

How do you update a JetBrains plugin for a new IntelliJ Platform version without breaking it?

Calls to APIs removed or deprecated in the target versions are replaced with their supported equivalent, the Gradle build is migrated to the current IntelliJ Platform Gradle Plugin and its new configuration, and the plugin is built and tested under the new Kotlin compiler mode where the target versions require it. Every Plugin Verifier error and warning for each target version is resolved or explained, and the changes ship as a pull request that builds green against each IDE version in scope.

What is the difference between a minor and a major plugin update?

A minor update covers deprecated APIs, the move to the current Gradle plugin and Plugin Verifier warnings. A major update covers removed APIs, the new Kotlin compiler mode, or a plugin with several modules. Both are delivered as a pull request with the Plugin Verifier report for every version you support.

Who it is for

  • Plugin vendors whose plugin breaks, or shows a compatibility warning, on a new IDE release.
  • Companies with an internal plugin that lags behind the IntelliJ version their developers now run.
  • Teams that want a plugin ready for the next IDE version before it ships, not after users report breakage.

What the update covers

  • Removed and deprecated APIs. Calls to APIs removed or deprecated in the target versions, replaced with the supported equivalent.
  • Kotlin K2 mode. The plugin built and tested under the K2 compiler where the target versions require it.
  • IntelliJ Platform Gradle Plugin 2.x. The build migrated to the 2.x plugin and its new configuration.
  • Plugin Verifier failures. Every Plugin Verifier error and warning for each target version resolved or explained.

What you receive

  • The changes as a pull request, building green against each IDE version in scope.
  • The Plugin Verifier report for each target version.
  • A written list of the API changes that were resolved.
  • One round of follow-up questions by email after delivery.

How it works

  • You share the plugin repository and the IDE versions it needs to support.
  • Within 2 business days you receive the scope in writing: versions, Minor or Major, delivery date and price.
  • 50% is paid when the work starts and 50% on delivery.
  • The work is asynchronous: email and the pull request. A call is available if you prefer one.

Price

  • USD 4,500, fixed (Minor), for deprecated APIs, the IntelliJ Platform Gradle Plugin 2.x and Plugin Verifier warnings, delivered within 5 business days.
  • USD 9,000, fixed (Major), for removed APIs, Kotlin K2 mode, or a plugin with several modules, delivered within 10 business days.
  • Paid by international bank transfer in USD, against an invoice.

Terms in short

  • The changes are yours once the invoice is paid.
  • Your code and your data stay confidential. Signing your NDA is fine.
  • The update targets the versions in scope and cannot promise a future IDE release will not change again. Liability is limited to the price paid.

Track record

  • It is the same process that keeps this catalog’s 146 plugins compatible with each new IntelliJ release: see the plugin catalog.
  • Root-cause work inside the IntelliJ Platform itself, reported to JetBrains: see the JetBrains Platform tickets.

Start