0.4.0

Add extension for synchronous iterative dispatch for messages (OSK-11…

0.3.1: Fix Messaging issues with IMessage Abstractions/Builder (OSK-9) (#10)

Motivation
----
The current message center builder and dispatcher interface is
incorrectly setting message types when attempting to get the message
boxes as well as not providng the correct message box list

Modifications
----
* Update IMessageDispatcher interface to pass the message type properly
* Updated MessageCenterBuilder to properly send the message boxes to the
message center
* Updated MesageCenter to properly handle the message type

Result
-----
Messages are transmitted as expected

Fixes #9

0.3.0: Remove output from delivery mechanisms (OSK-7) (#8)

Motivation
----
The output response for delivery mechanisms is adding unnecessary
complexity. Removing it to make the API easier to use and understand.

Modifications
----
* Removed the output response from the delivery mechanism APIs.

Result
----
A simpler API for delivery mechanisms without the need to handle output
responses.

Fixes #7

0.2.0: Refining SDK for Abstraction Usage (#6)

Motivation
----
The current implementation couples a bunch of shared logic/interfaces to
the main messaging implementation in `OSK.Messages.Messaging`. While
this works, it's not ideal for projects that don't necessarily need or
want to add a dependency on the core implementation for OSK (i.e.
courier integrations, recipient-only libraries, etc.) where the core
logic would add extra cruft that isn't required for the project.

Modifications
----
* Moved the main interfaces and data structures related to the Courier
and Message Recipient integrations into the abstraction layer, so the
core implementation for messaging can be ignored when not needed
* Refactored the system to drop the requirement of message <T> types for
the interfaces and instead use generic non-typed interfaces/data
structures for the integration and usage of the library. Only when
messages are sent will <T> types be used

Result
----
The library is a bit easier to integrate with in certain scenarios not
requiring the usage of the main message implementation

Fixes #5

0.1.1: Update the project files for missing nuget information (OSK-3) (#4)

Motivation
----
Some nuget information was missed in the original PR

Modifications
----
* Added missing nuget information to the project files

Result
----
Nuget packages are more complete

Fixes #3

0.1.0: Add initial project (OSK-1) (#2)

Motivation
----
Need a project that can send, receive, and deliver messages for
applications

Modifications
----
* Added project:
* Handle messages via a Dispatcher -> Courier -> Message Center -> Box
-> Recipient pattern
* Added projects for abstractions, messaging (core), and a simple
runtime
  * Added Unit Tests
  * Github workflows

Result
----
A project is available that can handle messages in application(s)

Fixes #1