@7365admin1/core 3.47.1-staging.125 → 3.47.1-staging.126
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.changeset/console-audit-client-status.md +20 -0
- package/dist/index.js +817 -808
- package/dist/index.js.map +1 -1
- package/dist/index.mjs +806 -797
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
- package/test/console-audit.test.mjs +69 -11
|
@@ -0,0 +1,20 @@
|
|
|
1
|
+
---
|
|
2
|
+
"@7365admin1/core": patch
|
|
3
|
+
---
|
|
4
|
+
|
|
5
|
+
Suspending or reactivating a client is now recorded in the console audit trail.
|
|
6
|
+
|
|
7
|
+
The audit trail (`console-audit`) already carried `client.suspended` and
|
|
8
|
+
`client.reactivated` with their labels and their allow-listed fields, but nothing
|
|
9
|
+
wrote them: `organization.controller.ts` was deliberately left unhooked while the
|
|
10
|
+
suspend work was still an open PR. Now that it has landed, `updateStatus` records
|
|
11
|
+
one row per status change - the direction taken from the status that was actually
|
|
12
|
+
written, the actor taken from the owner guard's return value and never from the
|
|
13
|
+
request body, and only `status` kept from the change.
|
|
14
|
+
|
|
15
|
+
The row is written after the status has changed and before the reply, the same
|
|
16
|
+
order as every other recorded action, so a row can never describe something that
|
|
17
|
+
did not happen. `recordConsoleAction` still swallows its own failures, so a lost
|
|
18
|
+
audit row cannot undo a suspension.
|
|
19
|
+
|
|
20
|
+
`client.created` stays unconnected on purpose and its reminder is unchanged.
|