Release notes

This page tracks recent capabilities on the MatrixFlow development branch used by the MOI 5.0 documentation. For production, use release tags, deployment notices, and the version shown by the environment as the source of truth.

July 22, 2026 development snapshot

Identity and authorization

  • Integrated M2–M4 canonical authorization; role and resource authorization decisions are beginning to be handled uniformly by Core IAM while maintaining fail-closed behavior.

  • Completed the UC Personal Access Token (PAT) authentication flow.

Agents and automation

  • Updating an automation task now redeploys enabled workflows.

  • Agent feedback uses message_id as its unique anchor and backfills message ownership.

  • Strengthened A2A conversation persistence, delayed titles, and runtime recovery for Catalog document agents.

Data processing and models

  • Added a dedicated Parse V3 workflow template and made moi:parse V3 the default document-parsing node.

  • DOCX OpenXML parsing now supports page_selector and the geometry runtime.

  • Embedding models can declare an optional image subtype.

  • Knowledge-base reconciliation writes chunks in batches, reducing write overhead when processing large numbers of chunks.

Upgrade checks

  1. Permission-related integrations should validate effective roles, workspace resolution, and fail-closed behavior, and should not rely on legacy permission-code fallback.

  2. For workflows that use legacy parsing templates, determine whether they need to migrate to Parse V3, and regression-test DOCX page-selection results.

  3. After updating an automation task, check its redeployment status and confirm that its trigger parameters and target version match.

  4. Run a fixed set of regression tasks for knowledge bases, agents, and model integrations, retaining execution IDs and error information.