KamoCRM

Split Available on the catalog verdict, and stop Stage publishing an app

Fixkamo-internal
Shipped
9 ஆகஸ்ட், 2026 அன்று 2:07 AM UTC
Author
kamo
Commit
d6882dc

The account Apps tab derived Available / Not Available from development stage, so it contradicted the platform catalog the moment an operator published or withheld something. It now reads the available flag the features payload carries, falling back to stage so an older SecurityService keeps todays behaviour rather than showing every app as unavailable. The platform Apps and Features tab sent available as null whenever it matched the shipped default, to keep unedited distinguishable from edited-to-the-same-value. That is sound for the text fields but not for this one: the servers fallback for a null available is stage-derived, so changing Stage silently published or withheld the app — a field the operator was not editing. It is always sent explicitly now. Also the last place a negotiated add-on rendered as $0.00: the add-on picker on the subscription detail page.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing