Skip to content

Backport #81455 to 25.3: Bump orc to 2.1.2#81612

Merged
thevar1able merged 2 commits into25.3from
backport/25.3/81455
Jun 30, 2025
Merged

Backport #81455 to 25.3: Bump orc to 2.1.2#81612
thevar1able merged 2 commits into25.3from
backport/25.3/81455

Conversation

@robot-ch-test-poll3
Copy link
Copy Markdown
Contributor

Original pull-request #81455
Cherry-pick pull-request #81476

This pull-request is a last step of an automated backporting.
Treat it as a standard pull-request: look at the checks and resolve conflicts.
Merge it only if you intend to backport changes to the target branch, otherwise just close it.

The PR source

The PR is created in the CI job

@robot-ch-test-poll3 robot-ch-test-poll3 added the pr-backport Changes, backported to release branch. Do not use manually - automated use only! label Jun 10, 2025
@clickhouse-gh
Copy link
Copy Markdown
Contributor

clickhouse-gh bot commented Jun 10, 2025

Workflow [BackportPR], commit [c14e4ea]

@larryluogit
Copy link
Copy Markdown
Contributor

@thevar1able Will there be another PR to backport orc upgrade to 25.3, which has CVE-2025-47436 as well?

@rschu1ze rschu1ze reopened this Jun 18, 2025
@rschu1ze
Copy link
Copy Markdown
Member

@thevar1able Sorry to re-open this, our friends at IBM asked kindly specifically for a backport of ORC bump to 25.3, so if we could backport it, it would be great.

@thevar1able thevar1able merged commit 96a8a3d into 25.3 Jun 30, 2025
11 of 29 checks passed
@thevar1able thevar1able deleted the backport/25.3/81455 branch June 30, 2025 05:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pr-backport Changes, backported to release branch. Do not use manually - automated use only!

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants