New Bug-Fix Releases Are Available for MPS

Releases
New Bug-Fix Releases Are Available for MPS – 2025.3.1, 2025.2.3, and 2025.1.3
We’ve released updates for multiple major MPS versions that fix several additional issues.
What’s new
Among the shared updates, two fixes backported from 2026.1 are worth highlighting:
- MPS-38409 – The new
read-only-inspector
style applies the read-only property to all editor cells in the inspector. When this style is applied to a cell in the main editor, the inspector becomes read-only for the inspected node while that cell is selected. - MPS-37407 – The Help menu on macOS now displays items with the correct height and spacing.
Check out all the updates in each particular version below:
MPS 2025.3.1
Download MPS 2025.3.1 here.
See the full list of fixed issues here.
MPS 2025.2.3
Download MPS 2025.2.3 here.
See the full list of fixed issues here.
MPS 2025.1.3
Download MPS 2025.1.3 here.
See the full list of fixed issues here.
Your JetBrains MPS team

Facts Only

* Bug-fix releases are available for MPS versions 2025.3.1, 2025.2.3, and 2025.1.3.
* Two fixes were backported from 2026.1.
* One fix implements the new read-only-inspector style, applying the read-only property to all editor cells in the inspector when a cell is selected in the main editor.
* Another fix updates the macOS Help menu to display items with correct height and spacing.
* Downloads are provided for MPS 2025.3.1, 2025.2.3, and 2025.1.3.

Executive Summary

New bug-fix releases are available for multiple major MPS versions, specifically 2025.3.1, 2025.2.3, and 2025.1.3. These updates address several issues across these versions. Two specific fixes backported from version 2026.1 include an update for the read-only-inspector style, which applies the read-only property to all editor cells in the inspector when applied to a selected cell in the main editor. Another fix addresses the macOS Help menu by ensuring items display with correct height and spacing. Users can download each specific version and access the full list of fixed issues for each release.

Full Take

The release structure focuses on delivering specific, targeted quality-of-life improvements alongside bug fixes across several software iterations. The backported nature of the updates suggests an effort to maintain consistency and address persistent issues across different major releases, indicating a commitment to long-term stability rather than isolated patch deployment. The inclusion of feature parity fixes (like the inspector style update) alongside interface refinements (the Help menu spacing) implies a system where underlying structural changes are simultaneously polished for user experience. A pattern emerges around version management: by releasing updates across multiple recent major points, the entity is managing complexity and ensuring that incremental improvements do not conflict with established baseline functionality. The implication is that stability and user experience refinement are treated as equally weighted components of the release cycle, positioning the maintenance of interface logic (like the inspector behavior) alongside basic navigational coherence.
What level of system-wide architectural change necessitated these specific backports? How does the sequencing of bug fixes across versions influence a user's perception of overall product maturity? What criteria are used to determine which fixes are prioritized for backporting versus those released only in the current version?