Merge tag 'v3.0.0-rc.1' into develop

Move messages to toolkit and introduce command queuer

Author: lindyhopchris

CHANGELOG.md

@@ -5,6 +5,8 @@ All notable changes to this project will be documented in this file. This projec
 
 ## Unreleased
 
+## [3.0.0-rc.1] - 2025-01-12
+
 ### Added
 
 - Commands can now be queued by the presentation and delivery layer via the `CommandQueuer` port. Refer to the command

docs/guide/upgrade.md

@@ -1,5 +1,34 @@
 # Upgrade Guide
 
+## 2.x to 3.x-rc.x
+
+Upgrade using Composer:
+
+```bash
+composer config minimum-stability rc
+composer require cloudcreativity/ddd-modules:^3.0
+```
+
+### Messages
+
+The message interfaces have been moved to the toolkit namespace. This is to make it clearer that these are part of the
+toolkit, not the application or infrastructure layers. It matches the `Result` and `Error` interfaces that are already
+in the `Toolkit\Result` namespace. I.e. now the toolkit contains both the input and output interfaces.
+
+This is a quick upgrade if you do a search and replace for the following:
+
+- `Contracts\Application\Messages` => `Contracts\Toolkit\Messages`
+
+### Command Queuing
+
+Previously the command bus had a `queue()` method on it. This has been removed and replaced with a new `CommandQueuer`
+interface. This is documented in the [Commands chapter.](./application/commands.md#command-queuer)
+
+The upgrade is relatively easy. You'll need to expose a new `CommandQueuer` driving port. Then wherever in your
+presentation and delivery layer that you need to queue a command, import that port instead of the `CommandBus` port.
+
+The documentation provides guidance on how to set up a command queuer port.
+
 ## 1.x to 2.x
 
 Upgrade using Composer: