Skip to content

Commit ee5da23

Browse files
committed
chore(changeset): admin field help and the hidden access-review pair
Claude-Session: https://claude.ai/code/session_01RsXNmkeex9WY5XsjNwtRYv Co-authored-by: Claude <noreply@anthropic.com>
1 parent d798d39 commit ee5da23

1 file changed

Lines changed: 24 additions & 0 deletions

File tree

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
'@objectstack/platform-objects': patch
3+
'@objectstack/metadata-core': patch
4+
'@objectstack/plugin-security': patch
5+
'@objectstack/plugin-approvals': patch
6+
'@objectstack/service-messaging': patch
7+
'@objectstack/objectql': patch
8+
---
9+
10+
fix: Setup field help is written for administrators, and the two access-review fields nothing uses yet are hidden from the Setup forms
11+
12+
Clause-②: no
13+
Metadata-protocol: none
14+
15+
A Setup pass met field help written for the platform's developers: "Foreign key to sys_user.id", "NULL only on a grant written before the column existed", "via isGrantActive", "(P3 digest middleware)", "Owned by objectql (better-auth is oblivious to this column)", "LifecycleService (Reaper / Rotator / Archiver)" and ADR numbers. Each now says what the field means and what to do with it, in every shipped locale (`en` regenerated from the source; `zh-CN`, `ja-JP` and `es-ES` translated):
16+
17+
- the user, OAuth application, session and refresh-token fields of the permission-set and position assignments and of the OAuth token, consent and client-resource objects, and the package-version field of stored metadata;
18+
- the permission set picked on an assignment;
19+
- the start time of an approval delegation;
20+
- the digest cadence and quiet hours of a notification preference, which now say how each value behaves;
21+
- the AI Access and Locale fields of a user;
22+
- the Data Lifecycle settings page and its retention overrides.
23+
24+
`Last Certified At` and `Certified By` on `sys_user_permission_set` and `sys_user_position` are reserved for a future access-review feature and nothing writes or reads them. They are now `hidden: true`, so the Setup forms and detail pages no longer show them. The columns and any stored values stay.

0 commit comments

Comments
 (0)