v1.0 marks the end of active development of Event Machine. It is used in a variety of projects. Those projects can finally rely on a stable version without the risk of breaking changes.

A few months ago we've started development of Event Machine v2.0 and along the way decided to change the project name, code namespace and the home of the project. It's now called Event Engine. You can find more information about that move here: https://github.com/event-engine/php-engine/releases/tag/v0.1.0

We still support Event Machine with bugfixes, but no further feature development. All new features depend on the refactored core used in Event Engine. If you plan to start a new project and want to use Event Machine, please consider usage of Event Engine instead! The two systems are NOT compatible. Even though, many concepts used in Event Machine are also used in Event Engine, for example the Descriptions to configure the message flow and the Flavours.

If you want to switch your existing project to Event Engine, feel free to contact us! We can provide guidance if needed.

Fixed

• #113 : OopFlavour should only decorate first recorded event

Added

• #111 Allow command preprocessors to stop dispatch

Added

• #108 - Introduce Flavours, see PR description for details

Changed

• #105 Provide access to DI container during tests
  • !BC BREAK! EventMachine::bootstrapInTestMode() returns ContainerInterface now

Fixed

• #104 Integer is also valid float type

Added

• #101 Add interfaces to avoid coupling with Event Machine in process managers and finders

Fixes

• Unset read models in ReadModelProxy after deletion

Fixed

• AggregateProjector should only drop collection if it exists

Small correction for bugfix release https://github.com/proophsoftware/event-machine/releases/tag/v0.17.1