Release Notes
Release history for MatrixEasyMode, including deployment notes, operational changes, and upgrade guidance.
Use this section to understand what changed between MatrixEasyMode versions before updating your deployment.
For installation, operations, and troubleshooting guidance, refer to the main documentation.
This section tracks published MatrixEasyMode releases from a deployment and operational perspective.
The goal is not only to announce new versions, but also to help users understand:
- what changed
- whether the release affects deployment or operations
- whether configuration review is recommended
- whether any manual upgrade steps exist
- what to verify after updating
MatrixEasyMode is still evolving quickly, so release notes should be treated as part of the normal upgrade workflow.
How to use this section
For each release, expect notes to cover:
- release overview
- deployment impact
- operational considerations
- upgrade guidance
- links to related documentation where needed
Smaller releases may only contain a few notes.
Larger releases that affect runtime behavior, ingress, configuration, deployment flow, or infrastructure assumptions should describe those changes explicitly.
Current releases
Upgrade approach
Before upgrading MatrixEasyMode, it is recommended that you:
- read the release notes for the target version
- review the Upgrading guide
- confirm your
.envstill reflects your intended deployment - confirm whether you are using registry mode or local mode
- verify the deployment after the upgrade completes
For most environments, deliberate upgrades are preferred over automatic or blind image updates.
Typical post-upgrade checks
After upgrading, it is recommended to verify:
- the web frontend is reachable
- the API is reachable
- Nginx Proxy Manager routes still exist and behave correctly
- logs do not show unexpected startup or ingress errors
- expected public URLs are working normally
Typical commands:
./stack.sh status
./stack.sh logs appRelease philosophy
MatrixEasyMode release notes aim to stay practical and operationally useful.
That means the focus is on:
- deployment impact
- runtime expectations
- upgrade clarity
- infrastructure behavior
- troubleshooting visibility
rather than marketing-style release announcements.