You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We cannot open this backport PR. Our standing rule is that maintainers own backports and release branches, so we do not open PRs into v0.11.0. To make the backport fast, I tested the cherry-picks against origin/v0.11.0 (eeebd1ece). All six PRs apply. Three need the same one-line conflict resolution.
The PRs were merged as merge commits, so -m 1 is necessary. The order is the merge order on main:
The conflicts are in examples/client-v2-json-processors/pom.xml, examples/jdbc-v2-json-processors/pom.xml and examples/demo-spring-service/pom.xml. In all three, the line next to the change is <clickhouse-java.version>. It is 0.11.0-rc1-SNAPSHOT on v0.11.0 and 0.12.0-rc1-SNAPSHOT on main. To resolve: keep the branch value of clickhouse-java.version, and take all other lines from the PR. For #3223, this means you also remove testcontainers.version and its comment, as the PR does on main.
Result: 9 files, +21/−29. These are the changes of the six PRs and no other lines.
mvn -B -DskipTests -Dmaven.javadoc.skip=true install on the result: BUILD SUCCESS, all 9 reactor modules (JDK 17 + JDK 8 toolchain). I did not run the tests. I did not build examples/ and performance/, because they are not in the root reactor.
I cannot open this PR yet. Our current rules do not let me open PRs into release branches, so I need approval from the operator of this bot. I asked for that approval for this issue, #3231 and #3232. When I have the decision, I reply here.
The recipe in my previous comment is still valid: v0.11.0 is still at eeebd1ece. If you do not want to wait, it gives the same change.
Update 2026-10-20: The operator approved. I will open the PR into v0.11.0 when the rule change is live. The PR will link this issue.
Activity
chernser commentedon Oct 20, 2026
@polyglotAI-bot fix this please
polyglotAI-bot commentedon Oct 20, 2026
We cannot open this backport PR. Our standing rule is that maintainers own backports and release branches, so we do not open PRs into
v0.11.0. To make the backport fast, I tested the cherry-picks againstorigin/v0.11.0(eeebd1ece). All six PRs apply. Three need the same one-line conflict resolution.The PRs were merged as merge commits, so
-m 1is necessary. The order is the merge order onmain:The conflicts are in
examples/client-v2-json-processors/pom.xml,examples/jdbc-v2-json-processors/pom.xmlandexamples/demo-spring-service/pom.xml. In all three, the line next to the change is<clickhouse-java.version>. It is0.11.0-rc1-SNAPSHOTonv0.11.0and0.12.0-rc1-SNAPSHOTonmain. To resolve: keep the branch value ofclickhouse-java.version, and take all other lines from the PR. For #3223, this means you also removetestcontainers.versionand its comment, as the PR does onmain.Result: 9 files, +21/−29. These are the changes of the six PRs and no other lines.
mvn -B -DskipTests -Dmaven.javadoc.skip=true installon the result:BUILD SUCCESS, all 9 reactor modules (JDK 17 + JDK 8 toolchain). I did not run the tests. I did not buildexamples/andperformance/, because they are not in the root reactor.chernser commentedon Oct 20, 2026
@polyglotAI-bot I'm a maintainer and asking you do the PR to
v0.11.0for me I'll reviewpolyglotAI-bot commentedon Oct 20, 2026
I cannot open this PR yet. Our current rules do not let me open PRs into release branches, so I need approval from the operator of this bot. I asked for that approval for this issue, #3231 and #3232. When I have the decision, I reply here.
The recipe in my previous comment is still valid:
v0.11.0is still ateeebd1ece. If you do not want to wait, it gives the same change.Update 2026-10-20: The operator approved. I will open the PR into
v0.11.0when the rule change is live. The PR will link this issue.chernser commentedon Oct 21, 2026
all merged