Prepare v1.4.0 release

Author: mape1402

.release

@@ -1 +1 @@
-v1.3.0
+v1.4.0

CHANGELOG.md

@@ -4,6 +4,8 @@ All notable changes to Mule packages will be documented in this file.
 
 ## [Unreleased]
 
+## [v1.4.0] - 2026-08-18
+
 ### Added
 
 - Added a bounded lane action executor that separates reading/claiming from action execution.

README.md

@@ -378,6 +378,8 @@ With FastLane Redis, foreground enqueue writes to Redis first and returns withou
 
 Redis does not replace EF Core durable storage. Treat it as a fast shared front buffer in front of the durable provider. If Redis is configured with volatile persistence or data is evicted before Mule flushes it, unflushed intents can be lost. Use Redis persistence and memory policies that match the durability window your workload can tolerate.
 
+For high-throughput workloads, tune `IntentFlushSize` and `CompletionFlushSize` together with `DispatchBatchSize`, `ExecutionQueueCapacity`, and lane `MaxDegreeOfParallelism`. Larger flush batches reduce durable storage round trips; larger dispatch batches reduce Redis claim overhead. Keep `LeaseDuration` comfortably above the normal execution time for an action so another replica does not reclaim work that is still running.
+
 ## Dispatcher Settings
 
 Configure concurrency, retry, recovery, locking, and cleanup through `MuleSettings`: