@shivaedev/test-story 0.47.0 → 0.47.2

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/CHANGELOG.md CHANGED
@@ -1,5 +1,18 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.47.2 - 2026-11-18
4
+
5
+ ### Changed
6
+
7
+ - Update `@shivaedev/contract` from 0.44.0 to 0.45.0.
8
+ - Update `@shivaedev/test-sql` from 0.25.0 to 0.25.1.
9
+
10
+ ## 0.47.1 - 2026-11-11
11
+
12
+ ### Changed
13
+
14
+ - Update `@shivaedev/test-sql` from 0.24.9 to 0.25.0.
15
+
3
16
  ## 0.47.0 - 2026-11-11
4
17
 
5
18
  ### Added
package/README.md CHANGED
@@ -649,7 +649,7 @@ accounts.it("removing Bob ends his session", [bobIsSignedIn()], function* ({ rem
649
649
 
650
650
  Stories and kits never wait on real time: use the [controlled clock](#waiting-for-a-timer) for elapsed time and engine signals for completion. Real sleeps, wall-clock polling, `Date.now()` and real timers in test code are forbidden; a deadline that only bounds failure is allowed.
651
651
 
652
- Pass a UTC `DateTime` as the story's `clock` option to pin time before its wrapper, creation, traits and hooks run. Code that uses `Clock` or `DateTime.now` reads that instant. Advance it with native `TestClock.adjust` in a kit verb, so the spec names the time that passes:
652
+ Pass a UTC `DateTime` as the story's `clock` option to pin time before its wrapper, creation, traits and hooks run. Code that uses `Clock` or `DateTime.now` reads that instant until a verb advances the clock, so records written one after another carry the same timestamp. A story whose claim depends on their order advances the clock between the writes, and the query it reads ends its ordering with a [unique tie-break column](https://github.com/ShivaeDev/platform/blob/main/packages/sql/README.md#newest-rows-per-group-distinct-on-and-grouped-aggregates). Advance the clock with native `TestClock.adjust` in a kit verb, so the spec names the time that passes:
653
653
 
654
654
  ```ts
655
655
  import * as TestClock from "effect/testing/TestClock";
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@shivaedev/test-story",
3
- "version": "0.47.0",
3
+ "version": "0.47.2",
4
4
  "description": "Tests that read like stories over the real engine: a story kit per engine with its own it, traits per feature, and a failure that prints the story, where it stopped and the engine's state",
5
5
  "homepage": "https://github.com/ShivaeDev/platform/tree/main/packages/test-story#readme",
6
6
  "bugs": {
@@ -42,9 +42,9 @@
42
42
  "README.md"
43
43
  ],
44
44
  "dependencies": {
45
- "@shivaedev/contract": "0.44.0",
45
+ "@shivaedev/contract": "0.45.0",
46
46
  "@shivaedev/test": "0.17.2",
47
- "@shivaedev/test-sql": "0.24.9",
47
+ "@shivaedev/test-sql": "0.25.1",
48
48
  "dom-accessibility-api": "0.7.1"
49
49
  },
50
50
  "devDependencies": {
@@ -52,9 +52,9 @@
52
52
  "@effect/platform-node": "4.1.2",
53
53
  "@effect/sql-pg": "4.1.2",
54
54
  "@effect/vitest": "4.1.2",
55
- "@shivaedev/quality": "0.77.0",
56
- "@shivaedev/react": "0.47.2",
57
- "@shivaedev/server": "0.34.0",
55
+ "@shivaedev/quality": "0.78.1",
56
+ "@shivaedev/react": "0.48.0",
57
+ "@shivaedev/server": "0.34.2",
58
58
  "@types/node": "24.19.2",
59
59
  "@types/react": "19.3.0",
60
60
  "@types/react-dom": "19.3.0",