@signal-tree/angular 15.4.0 → 15.4.3

package/llms.txt

@@ -1,6 +1,6 @@
 # SignalTree
 
-This reference describes the 15.4.0 package version, with explicitly marked
+This reference describes the 15.4.3 package version, with explicitly marked
 15.3.1 comparisons. Consult the [npm package page](https://www.npmjs.com/package/@signal-tree/kernel?activeTab=versions)
 for published versions.
 
@@ -226,9 +226,12 @@ in existing v15. In 15.3.1, automatic refusal before a
 handle returns records surviving writes as committed, retains eligible undo
 history, releases consequences, and still throws. Successful automatic rollback
 reverses recorded writes. Error does not guarantee undo: never blindly retry the
-whole operation or use `undo()`/`jumpTo()` for request reconciliation. Removing a
-pending-created row after a confirmed edit does not necessarily clear its
-rollback dependency. Recoverable pending refusal is a v16 target, not v15 API.
+whole operation or use `undo()`/`jumpTo()` for request reconciliation. Since
+15.4.2, a pending-created or pending-rekeyed row removed by settled later work
+no longer blocks rollback; a pending-created row confirmed work edited and kept
+still refuses, so removal is not a general recovery strategy. After a rejection,
+`undo()` of a later write can restore the rejected transaction's speculative
+value. Recoverable pending refusal is a v16 target, not v15 API.
 
 15.3.1 containment covers deferred write subscribers and transaction turn
 listeners, not all framework effects. Vue watcher failures differ between
@@ -302,3 +305,13 @@ work, not a FIFO of application values. A tool recording these events owns its
 bounded retention and must show interruptions, omissions and unsupported sources.
 Unsubscribe on view teardown and destroy bounded-lifetime trees. See
 [Runtime observation in 15.4.0](https://github.com/JBorgia/signal-tree/blob/v15.4.0/docs/guides/runtime-observation.md) for contracts and examples.
+
+## Observer failures during undo and rollback (15.4.2)
+
+A reactive observer can throw after undo, redo or transaction rollback has
+already applied. SignalTree completes the operation's bookkeeping and rethrows
+the original value; a throw alone does not establish that state was unchanged.
+Reusing that error in a later failure before application does not make the later
+operation successful. Check current state and settlement/history status when
+handling failures. This does not provide atomic recovery for arbitrary user
+callbacks that partially mutate state before throwing.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@signal-tree/angular",
-  "version": "15.4.0",
+  "version": "15.4.3",
   "description": "Angular realization for SignalTree.",
   "license": "Apache-2.0",
   "type": "module",
@@ -25,7 +25,7 @@
     "llms.txt"
   ],
   "dependencies": {
-    "@signal-tree/kernel": "15.4.0"
+    "@signal-tree/kernel": "15.4.3"
   },
   "peerDependencies": {
     "@angular/core": "^20.0.0 || ^21.0.0 || ^22.0.0",