PyCharm Toolbox App vs. standalone installers: which rollback path after a failed upgrade?
19.5K reputation · 30 Oct 2023, 06:49 UTC
I'm planning a PyCharm upgrade (managed through the JetBrains Toolbox App) and want a solid recovery plan before I start. My understanding is that Toolbox keeps previous versions installed side by side, so recovery after a bad upgrade means launching the older build rather than reinstalling, and that the previous version's config directory is left intact for settings fallback.
Where I'm stuck is deciding between two strategies: relying on Toolbox-managed rollback versus keeping standalone installers of the prior release on hand. Toolbox channel settings (release vs. EAP) and its automatic-update option seem to affect which versions remain available and whether the IDE silently re-upgrades after I roll back. I also plan to export settings via File > Manage IDE Settings > Export Settings beforehand and commit all project files to VCS, since a newer IDE may migrate project configuration that a downgrade won't revert.
Plugins built against a specific IDE build number are my other concern, since incompatible plugins seem to be a common post-upgrade failure point.
Is Toolbox-managed rollback sufficient on its own, or is keeping standalone installers meaningfully safer? Does disabling automatic updates in Toolbox reliably prevent re-upgrade after a rollback? And should incompatible plugins be disabled before upgrading rather than after?