v4.5.1

🔧 Fixes

• Replies to stashed Asks are no longer dropped after Unstash / UnstashAll under concurrent load (#1312). Stash, Unstash, and UnstashAll clone the in-flight message into a pooled receive context without clearing the late-reply guard, so a recycled context silently dropped the reply sent with Response and the caller failed with request timed out. The clone path now clears the guard, and actor and grain Ask callers no longer write the guard on a context already handed to the mailbox, which could drop an unrelated request's reply.

🔀 Pull Requests

• #1313 fix(actor): stop dropping replies to stashed Asks after unstash by @Tochemey

Full Changelog: v4.5.0...v4.5.1