Upgrading

The CHANGELOG is the canonical record of every release — read it top-down for the versions you are crossing. Two changes deserve to be impossible to miss: one changes your security posture silently, the other breaks programmatic callers loudly (a 404):

0.1 → 0.2: separation of duties became opt-in (silent)

config.sod_actions now defaults to [] — empty means the SoD veto never runs. A 0.1 host that relied on the old default and never set sod_actions explicitly loses the veto on upgrade with no error and no warning. If you want SoD, say so:

config.sod_actions = %w[approve]

Tracked as #27 (a dedicated UPGRADING.md is planned).

0.2 → 0.3: management-UI route rename (loud — programmatic callers 404)

Org-wide role assignment is now resources :role_assignments (plural). A host that POSTs /current_scope/role_assignment (singular) or uses the old role_assignment_path / remove_role_assignment_path helpers gets a 404 on upgrade. The engine’s own UI is unaffected — this bites only direct path or helper callers. Details in the CHANGELOG errata.

Also in 0.2+

• Declared Rails floor is >= 8.1 (the management UI relies on params.expect array semantics introduced in 8.1).
• config.audit became tri-state false | true | :strict.