Repository navigation
4.0 upgrade guide - #339
Merged
Merged
Conversation
The hydrator option could no longer be disabled since the legacy hydrator is gone, so the enabled flag is removed. Also fix the configuration docs that still described dbal_aggregate and the old cryptography options.
DanielBadura
approved these changes
Oct 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
docs/UPGRADE-4.0.mdwith the breaking changes of the bundle since 3.x. Changes coming from event-sourcing 4.0 and hydrator 2.0 are only linked to their own upgrade guides.While writing it I noticed that
hydrator.enabledwas still accepted but did nothing anymore, because the legacy hydrator was removed. The option is gone now. I also fixed the configuration docs that still mentioneddbal_aggregate, theAggregateToStreamHeaderTranslatorand the old rootcryptographyoption.