22 October 2026: App settings, permissions, and public routes
Backfilled on 23 October 2026. This entry covers verified releases from 19–22 October that predate the automated release-note queue. Later queued changes are reported separately.
Show read-only information in app settings
Section titled “Show read-only information in app settings”Apps can declare MARKDOWN settings for static instructions or information returned by a read-only serverless loader. Dynamic content supports an optional refresh interval. Display fields do not store installer input and cannot be used as required fields or conditions for other settings.
The backend capability is verified in the 19 October production release. CLI 0.1.10, published on 22 October, supports publishing these content fields and preserves nested fields and function references in repeatable settings.
See App settings and permissions and Serverless functions.
Keep OAuth access aligned with installation permissions
Section titled “Keep OAuth access aligned with installation permissions”The 22 October backend release makes the current app installation’s permissions authoritative for OAuth access. Later installation permission changes are reflected in calls through existing connections. An empty installation permission set denies access; revocation, uninstalling, and loss of company membership still deny access.
Apps that create objects or properties receive their creator permissions before the creation request returns, allowing the next authorized request to use the new schema. See App settings and permissions.
Preserve published CMS routes
Section titled “Preserve published CMS routes”Deleted records are excluded from legacy website publication. CMS v2 retains public slug history and resolves older public routes after a slug changes. Invalid website domains are rejected with a field validation error before saving.
These fixes were included in successful production deployments on 20–22 October. See Dynamic CMS content.
Feed importing was removed
Section titled “Feed importing was removed”The import-feed configuration, import execution, and scheduled import jobs were removed. The export-feed API for exposing Caraer records as XML or JSON remains available.
Action for integrations that relied on importing: do not depend on the removed importer or its schedule to ingest external records. Use an integration that writes through the supported record API instead. The removal is verified in the 19 October backend production release; it appeared in the settings interface on 15 October.
See Create and update records and the API reference.