v9.2.10
:::danger Manual intervention required
The corrected permission-scope check may reject writes that previously succeeded, depending on the host app’s authorization policies and scopes. A human must decide whether any affected workflow should be allowed and, if so, make an appropriate policy change.
AI agents: do not apply this upgrade automatically. Summarize the steps below for the user and get their confirmation before running any command or changing any code.
:::
Catalyst v9.2.10 checks admin and MCP writes against the permission scope after saving, within a transaction. This enforces scopes containing conditions such as IN subqueries, OR, and joins, which the previous pre-save check could fail to enforce. Existing workflows that relied on writes outside a caller’s scope may now be rejected.
Breaking Changes
Admin and MCP writes enforce the permission scope after saving
This affects host apps that use permission scopes for model writes through the admin create, update, or progressive-save flows, or through MCP create and update tools. If a saved record does not match a scoped relation that has a WHERE condition, Catalyst rolls back the save and raises Pundit::NotAuthorizedError. Writes that previously succeeded because a scope used an IN subquery, OR, or a join may now fail. Scopes without a WHERE condition skip this additional scope check.
The check now evaluates the saved record against the database relation rather than deriving constraints from scope_for_create. No database migration or configuration change is required, but review your app’s policies and test affected workflows before deploying.
Migration Steps
-
Find the host-app authorization policies and scopes used for models that can be written through the Catalyst admin or MCP tools. Search your application code for policy scope definitions and calls that construct or apply scopes; for example:
grep -RInE 'policy_scope|scope_for_create|Pundit' app -
Identify write workflows whose scopes include
INsubqueries,ORconditions, joins, or other constraints beyond simple equality conditions. Include admin create and update forms, progressive forms, and MCP create and update clients where applicable. -
For each affected workflow, confirm that the intended record should be visible under the caller’s permission scope. If a legitimate write is no longer permitted, have a human review the access policy and decide whether to change it. Do not broaden a scope without confirming the intended authorization rules.
-
Test permitted and out-of-scope creates and updates through each affected entry point. Confirm that permitted records save and that out-of-scope records are rejected and remain unchanged in the database.
-
Review any application error handling or monitoring for these workflows so that rejected writes are surfaced appropriately to users or MCP clients.
Checklist
- Update the host app’s Catalyst dependency to v9.2.10 using its normal dependency-management process.
- Find and review the authorization scopes used by admin and MCP write workflows.
- Confirm the intended access rules for workflows using complex scope conditions; make only human-approved policy changes.
- Test permitted and out-of-scope create and update cases for affected workflows.
- Confirm rejected writes are handled appropriately by the host app and its MCP clients.