@unotest/viewer 0.33.0 → 0.35.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/CHANGELOG.md CHANGED
@@ -1,5 +1,44 @@
1
1
  # Changelog
2
2
 
3
+ ## [0.35.0] - 2026-09-15
4
+
5
+ ### Patch Changes
6
+
7
+ - Updated dependencies [79c99ab]
8
+ - Updated dependencies [dee96a1]
9
+ - @unotest/protocol@0.35.0
10
+ - @unotest/core@0.35.0
11
+ - @unotest/dsl@0.35.0
12
+
13
+ ## [0.34.0] - 2026-09-07
14
+
15
+ ### Patch Changes
16
+
17
+ - 32a495e: Failure artifacts survive a run that is isolated from its own artifact root.
18
+
19
+ A run executed inside a container sees only what is mounted into it. The
20
+ failure bundle's directory is derived from the artifact root, which on such
21
+ a run is not one of those mounts — so it could not be created, and a failed
22
+ test produced no screenshot, no trace and no page HTML at all. Worse, that
23
+ one error took the always-on copies in the run directory down with it: both
24
+ sinks shared a single try, so the artifact that does not depend on the
25
+ bundle was lost too.
26
+
27
+ Two changes. `UNOTEST_FAILURES_ROOT` now says where bundles live, for
28
+ whoever spawns the run to point at a directory it can actually write
29
+ (unset, everything behaves exactly as before). And the two sinks are
30
+ independent: an unusable bundle root no longer costs you the run
31
+ directory's screenshot and page HTML.
32
+
33
+ The viewer serves failure assets from either layout, so a bundle written
34
+ inside the environment's runs tree renders like a local one.
35
+
36
+ - Updated dependencies [32a495e]
37
+ - Updated dependencies [c6b91bb]
38
+ - @unotest/protocol@0.34.0
39
+ - @unotest/core@0.34.0
40
+ - @unotest/dsl@0.34.0
41
+
3
42
  ## [0.33.0] - 2026-09-06
4
43
 
5
44
  ### Minor Changes