Release v0.6.0: RubyMine 2025.3+ baseline and IDE 2026 stability fixes#101
Merged
Conversation
…m-template-2.6 Migrate Gradle and CI configuration
RubyMine 2026.1.1 throws "Read access is allowed from inside read-action only" when a row is selected in the routes table, because SimpleRoute lazily reads RailsAction.psiClass / psiMethod from getQualifiedActionTitle / getActionIcon / canNavigate / methodExists, all of which are invoked from the EDT (MainContent, ActionCellRenderer, RoutesTable double-click, RoutesTableFilter) outside of a read action. Capture the display-side values at init time inside the same ReadAction.run block as railsAction.update(), and have the getters return the cached snapshot. Navigation keeps using the existing ReadAction.nonBlocking re-resolution path so the jump target is still based on the latest PSI. Extract icon dispatch into a pure resolveActionIcon() helper so each branch (NodeRouteAction / NodeController / Unknown) can be unit-tested without the Ruby plugin services that are otherwise required to instantiate real RClass / RMethod under BasePlatformTestCase. Add SimpleRouteSnapshotTest covering: snapshot immutability, all three icon dispatch branches, default state with no Rails app, dynamic ":controller" routes, and the nested controller fallback (admin/users -> Admin::UsersController). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Raise minimum IDE to 2025.3 and fix PSI read assertion in 2026.1.1
Notify users when Rails Routes cannot run because the project has no module, no Rails application is detected, or no Ruby SDK is configured. Keep the reason visible in the tool window instead of silently returning to the initial state. Extract the preflight checks into a tested helper and run Rails application resolution inside a read action to avoid PSI read assertions. Also restore the Kotlin compiler daemon heap setting that was dropped during the Gradle migration. Tests: - ./gradlew check 🤖 Generated with https://claude.ai/code Co-Authored-By: Claude mailto:noreply@anthropic.com
fix: show configuration errors before running Rails Routes
The StubIndex can return non-RContainer elements such as RConstantImpl (e.g. when an `include SomeConstant` references a non-module constant). The previous unconditional `as RContainer` cast threw ClassCastException in that case and stalled the entire rails routes parsing. Replace it with an `is RContainer` smart cast so non-container matches are skipped and `null` is returned when no class/module is found. Tests: - ./gradlew check 🤖 Generated with https://claude.ai/code Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
rails routes is an external process that reads files from disk, so any in-editor edits to config/routes.rb (or related Ruby sources) that have not been written out yet will not be reflected in the result. Call FileDocumentManager.saveAllDocuments() at the action entry point, before launching the routes task, so the external process always sees the up-to-date contents. Tests: - ./gradlew check 🤖 Generated with https://claude.ai/code Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
fix: stop Rails Routes from stalling on cast errors and unsaved files
The Railroads tool window had two latent threading boundary gaps that violate IntelliJ Platform contracts: MainView was constructed off the EDT while walking the Swing component tree, and the mounted engine route resolved Ruby PSI / StubIndex outside a read action. Neither has produced a user-visible failure so far because today's UI callers happen to dispatch correctly and the mounted engine row is not reachable from the table double-click path. Newer platform builds ship stricter threading assertions that flag both as violations, so leaving them in place is borrowing trouble against the next platform bump. Add the platform contract assertions explicitly so any future bypass fails fast at construction / call time, rather than relying on platform-mode-dependent runtime checks that may or may not be active. Enabling mounted engine navigation from the UI (a canNavigate() override) is intentionally out of scope; this commit only makes the existing NavigationItem implementation safe for the callers that already invoke it. Tests: - ./gradlew check - Manual verification via ./gradlew runIde against a Rails app with mounted engines: no assertion violations in the IDE log, tool window renders normally, mounted engine row shows the expected icon and qualified title. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Enforce IntelliJ Platform threading contracts in routes view and mounted engine navigation
CopyRouteActionBase.update() reads the selected route through PlatformDataKeys.SELECTED_ITEM. When the data context is backed by RoutesTable, that path reads Swing selection/model state with selectedRow and convertRowIndexToModel(...), so the action update must run on the EDT. Switch the ActionUpdateThread contracts for CopyRouteActionBase and RouteCopyProvider from BGT to EDT. The update/copy paths only read route data already stored on BaseRoute and derive strings from routeName, routePath, and requestMethod, so this does not add PSI or index work to the EDT. Add tests covering the update-thread contract for CopyRouteNameAction, CopyRoutePathAction, CopyRouteFullPathAction, and RouteCopyProvider. Tests: - ./gradlew check - Manual verification via ./gradlew runIde against a Rails app: Copy Route Name / Path / Full Path each work for single and multi selection, with no assertion violations in the IDE log. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…hread-edt Move copy route action updates onto the EDT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
This PR merges the
epic/support_ide_2026branch intomainfor the v0.6.0 release.The branch raises the minimum supported RubyMine version to 2025.3 and includes the compatibility fixes needed for newer IDE 2026 platform builds, where stricter threading and read-action checks surfaced startup and route-loading failures.
The minimum supported IDE change is a breaking change for users on 2024.x, 2025.1, and 2025.2, so this is released as v0.6.0.
Summary
since-build = 253). Users on 2024.x, 2025.1, or 2025.2 should stay on the 0.5.x line.gradle.propertiesto0.6.0and updates the[Unreleased]CHANGELOG entry used for the v0.6.0 release notes.Included PRs
This PR consolidates the following already-reviewed PRs:
Notes
until-buildremains intentionally unset.v0.6.0draft release. Publishing that draft triggers the JetBrains Marketplace release and the changelog-update PR. Seedocs/release-process.mdfor the full runbook.Testing
SimpleRouteSnapshotTest,RoutesPreflightTest,CopyRouteActionBaseTest,RouteCopyProviderTest, andMountedEngineRouteTest.gradle.propertiesandCHANGELOG.md../gradlew patchPluginXml verifyPlugin buildPluginfor the bumped0.6.0version has not yet been run and should be run before merging this PR.