Bump the minimum Seata Client version for Seata AT integration to 2.2.0 #33872
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.
For #29052.
Changes proposed in this pull request:
org.apache.seata.core.rpc.netty.v1.ProtocolV1Decoder
andorg.apache.seata.core.rpc.netty.v1.ProtocolV1Encoder
have been renamed in feature: multi-version seata protocol support incubator-seata#6226client.rm.tableMetaCheckEnable
is nowtrue
, which completely breaks the logic of creating and destroying Seata Client in unit tests. This needs to be investigated on the Seata side. See Seata Client should allow dynamic monitoring of changes inservice.default.grouplist
incubator-seata#7039 .Before committing this PR, I'm sure that I have checked the following options:
./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e
.