@@ -2,6 +2,8 @@
 '@objectstack/plugin-approvals': patch
 ---
 
+**Shipped in 18.0.0-next.5**, whose CHANGELOG missed this entry; listed here one prerelease late.
+
 fix(plugin-approvals): the approval request page's highlights strip no longer shows the target object's API name
 
 Clause-②: no
 
@@ -3,6 +3,8 @@
 '@objectstack/spec': patch
 ---
 
+**Shipped in 18.0.0-next.5**, whose CHANGELOG missed this entry; listed here one prerelease late.
+
 feat(formula): `current_user.hasCapability(name)` — a page predicate can ask whether the viewer holds a system capability, from the same list the action gate reads
 
 Clause-②: yes (widening)
 
@@ -2,6 +2,8 @@
 '@objectstack/service-automation': minor
 ---
 
+**Shipped in 18.0.0-next.5**, whose CHANGELOG missed this entry; listed here one prerelease late.
+
 fix(service-automation): a `runAs: 'user'` flow now sees the acting user's organization members in `sys_user`, as the same user's own request does
 
 A `runAs: 'user'` flow's data nodes ran without `current_user.org_user_ids`, the peer list the request path resolves for every user. The shipped `sys_user_org_members` policy (`id in current_user.org_user_ids`) therefore dropped out, and a `get_record` on `sys_user` returned the acting user's own row only, while the same user's REST read returned their organization's members too.
 
@@ -2,6 +2,8 @@
 '@objectstack/spec': minor
 ---
 
+**Shipped in 18.0.0-next.5**, whose CHANGELOG missed this entry; listed here one prerelease late.
+
 A navigation entry whose `visible` reads `data` must declare `dataSource`: an entry with no `dataSource` whose `visible` predicate reads the top-level `data` root is refused at parse, at the entry's own `visible`, with the fix.
 
 Clause-②: no (narrowing)