Copilot Won’t Update in JetBrains? Check the IDE and Plugin Versions
You just updated IntelliJ, and the Copilot plugin download still fails with a build number in the error. Is that the minimum build, or a ceiling?
- The current Copilot plugin requires JetBrains IDE 2025.2 or newer.
- A newer IDE can also reject a plugin package built for an older platform.
- Compare the IDE build with the plugin’s compatibility range before reinstalling.
On 2025.1, update the IDE first
Copilot’s support floor has moved. The October 10 GitHub changelog says support for JetBrains IDE 2025.1 has ended and the plugin now needs 2025.2 or later.
The minimum is not the same as the recommended upgrade. Microsoft’s advance notice recommends 2026.1 or later while setting 2025.2.x as the minimum. A patch release such as 2025.1.7 is still part of the retired family.
Compare two versions, not just one
Record the running IDE’s version and build, then inspect the Copilot package’s supported range. “Latest” is not enough to identify whether a downloaded package fits your IDE.
- Open Help → About on Windows or Linux, or the IDE’s About menu on macOS.
- Open Settings → Plugins and find the installed GitHub Copilot version.
- Check its compatibility range on the official Marketplace Versions page.
- If the IDE is below the supported minimum, upgrade it before updating Copilot. Restart when prompted.
GitHub’s installation guide points to Marketplace for compatibility details. Use that listing when choosing a package instead of relying on an older download.
A new IDE can reject an old package
The opposite mismatch appears in Copilot feedback issue 1432: the package supported an older maximum platform build than the installed IntelliJ build. A maintainer directed the reporter to the package for newer IDEs, and an October 20 update confirmed that the correct build worked.
Read whether the error identifies a minimum or a maximum build. That historical package number is evidence of the mismatch, not a recommendation to install that version today.
| Situation | Next check |
|---|---|
| The IDE is 2025.1.x | Move to a supported IDE version. |
| A recent IDE rejects installation | Compare its build with the package’s lower and upper limits. |
| Installation succeeds but login or suggestions fail | Investigate the actual runtime error separately. |
Existing installations are not immediately switched off
Microsoft says an existing plugin is expected to keep working after support ends. It will no longer receive fixes, improvements or new features for that IDE version.
If your organization must keep an older IDE, distinguish today’s working installation from an environment that can receive future updates. For a failure on a supported IDE, report the IDE build, plugin version and exact error together so the compatibility claim can be checked.