@ultimat3/auth 17.0.0 → 19.0.0

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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ultimat3/auth",
3
- "version": "17.0.0",
3
+ "version": "19.0.0",
4
4
  "description": "Sessions, passwords, OAuth, MFA and api keys — resolved to one Actor",
5
5
  "license": "MIT",
6
6
  "type": "module",
@@ -24,15 +24,15 @@
24
24
  "LICENSE"
25
25
  ],
26
26
  "engines": {
27
- "bun": ">=1.3.0"
27
+ "bun": ">=1.4.0"
28
28
  },
29
29
  "scripts": {
30
30
  "typecheck": "tsc --noEmit -p tsconfig.json",
31
31
  "test": "bun test"
32
32
  },
33
33
  "dependencies": {
34
- "@ultimat3/core": "17.0.0",
35
- "@ultimat3/db": "17.0.0",
36
- "@ultimat3/schema": "17.0.0"
34
+ "@ultimat3/core": "19.0.0",
35
+ "@ultimat3/db": "19.0.0",
36
+ "@ultimat3/schema": "19.0.0"
37
37
  }
38
38
  }
@@ -17,8 +17,10 @@ const WHOLE_NON_NEGATIVE = 'a whole number of zero or more';
17
17
  * counts, and past 2^53 a double cannot name its own successor — a "duration" up there is already
18
18
  * a rounded one, and `now + it` no longer moves.
19
19
  *
20
- * The `Finite` in the name is load-bearing: `bun run finite-bounds` recognises a repair by the
21
- * shape of the CALL, so a screen named `whole` left every call site reading as unchecked.
20
+ * The `Finite` in the name is NOT load-bearing, `As of 2026-08-26`. It was: `bun run
21
+ * finite-bounds` matched a repair on the callee's NAME, so a screen named `whole` left every call
22
+ * site reading as unchecked. It now reads `SCREENING_CALLEES` in `scripts/lib/finite-screens.ts`,
23
+ * so a rename is a row edit rather than a gate failure.
22
24
  */
23
25
  export function assertFiniteAuthCount(
24
26
  key: string,