Merge release 3.22.0 into 4.0.x - #918
Merged
Merged
Conversation
* on versioned branches only trigger deploy if a changed landed in the docs * on release always trigger deploy
Improve docs deployement to minimise CI times
| datasource | package | from | to | | ---------- | ------- | ---- | --- | | docker | php | 8.3 | 8.5 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
| datasource | package | from | to | | ---------- | ------- | ---- | -- | | docker | mariadb | 12 | 13 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Update php Docker tag to v8.5
Update mariadb Docker tag to v13
| datasource | package | from | to | | ---------- | ------- | ---- | -- | | docker | mysql | 8 | 26 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Update mysql Docker tag to v26
…ay happen that an already handled subscription appear unhandled for the engine due how mysql/mariadb work regarding affected rows. Also fix an api gurantee issue: catch unqiue constraint exception from doctrine and throw a subscription already exists exception
* drop index via task could have not worked due to casing issues * dont claim lock idefinelty with mysql/mariadb if lock could not aquire * event criterion passed wrong param type to dbal * cipher key store could return random key for one subject if mutliple existed
…GQ6FRTo Merge release 3.21.2 into 3.22.x
…is active and exactly 7281 messages were saved that the setval was not called
Fix save of multiple messages when `keep_index` used and exact 7281 messages saved
…wtQcaUO Merge release 3.21.3 into 3.22.x
…-commit Fix lock timing for mysql/mariadb: handle lock outside the transaction
…LdqrWiL Merge release 3.21.4 into 3.22.x
…x` was only incremented by one instead of set to the yielded index. The next event was then treated as a new gap, the loader reloaded from the old position and yielded the event after the gap again. Batching subscribers handled that event twice.
Update roave/backward-compatibility-check to ^8.23.0
…alisation / registration Ref: #524
Add custom stream docs
…7iANmaW Merge release 3.21.5 into 3.22.x
Add header aliases
| datasource | package | from | to | | ---------- | ----------------- | ----- | ------ | | packagist | league/commonmark | 2.9.0 | 2.10.2 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
# Conflicts: # docs/cli.md # src/Cryptography/ExtensionDoctrineCipherKeyStore.php # src/Store/DoctrineDbalStore.php # src/Store/StreamDoctrineDbalStore.php # src/Subscription/Engine/GapResolverStoreMessageLoader.php # src/Subscription/Store/DoctrineSubscriptionStore.php # tests/Integration/Store/DoctrineDbalStoreTest.php # tests/Integration/Store/StreamDoctrineDbalStoreTest.php # tests/Unit/Console/Command/SubscriptionStatusCommandTest.php # tests/Unit/Message/Serializer/DefaultHeadersSerializerTest.php # tests/Unit/Metadata/Message/AttributeMessageHeaderRegistryFactoryTest.php # tests/Unit/Metadata/Message/MessageHeaderRegistryTest.php # tests/Unit/Store/DoctrineDbalStoreTest.php
Author
|
Hello 👋 here is the most recent benchmark result:
This comment gets update everytime a new commit comes in! |
…Store The fixes that came in with the 3.22 upmerge only touched the stream store. The taggable store had the same problems: the event id criterion was bound as array parameter, the mysql/mariadb lock was released before the commit, and a failed lock acquisition left hasLock set so later calls skipped locking. configureSchema also compared connection instances instead of checking for the same database. The integration tests added for the stream store are ported as well.
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
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.
Release Notes for 3.22.0
Feature release (minor)
3.22.0
enhancement