Release 2026.2

[hurricup]

Summary by CodeRabbit

• Chores
  • Updated the IntelliJ Platform build baseline to the 2026.2 release line.
  • Refreshed platform, Java, plugin, and verification components to compatible versions.
  • Updated plugin build metadata for the new platform release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b1842690-4ec9-49e5-94ef-fa3f3c847116

📥 Commits

Reviewing files that changed from the base of the PR and between d7e95e6 and f246107.

📒 Files selected for processing (2)

• gradle.lockfile
• gradle.properties

---

📝 Walkthrough

Walkthrough

The build metadata now targets IntelliJ 2026.2, clears obsolete EAP identifiers, and updates the Gradle lockfile to matching bundled, platform, compiler, and verifier dependency coordinates.

Changes

IntelliJ platform baseline

Layer / File(s)	Summary
Platform and plugin metadata gradle.properties	The target platform changes to 2026.2, while platform branch, plugin version, plugin branch, and plugin build values are cleared.
Locked platform dependencies gradle.lockfile	Bundled modules, plugins, IntelliJ artifacts, and verifier mappings are updated to match the new platform coordinates.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• Camelcade/Perl5-IDEA#3211: Updates the Gradle lockfile and IntelliJ platform baseline metadata.
• Camelcade/Perl5-IDEA#3068: Changes the IntelliJ platform version and branch metadata.
• Camelcade/Perl5-IDEA#3190: Adjusts the plugin build metadata in gradle.properties.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title matches the main change: updating the project to the 2026.2 release baseline and related IntelliJ platform metadata.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch hurricup/20262

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

Qodana for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked
☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[coveralls]

coverage: 75.997% (-0.03%) from 76.024% — hurricup/20262 into master