Skip to content

Forward port 5.0: Add more porting workflows#16287

Merged
chrisvest merged 1 commit into5.0from
forwardport-pr-16283-to-5.0
Feb 17, 2026
Merged

Forward port 5.0: Add more porting workflows#16287
chrisvest merged 1 commit into5.0from
forwardport-pr-16283-to-5.0

Conversation

@netty-project-bot
Copy link
Copy Markdown
Contributor

Forward port of #16283 to 5.0
Cherry-picked commit: 6c611ec


Motivation:
Following the success of #16273 we should also have workflows for porting 4.2 -> 5.0, and 5.0 -> 4.2.

Modification:
Copy the 4.2 -> 4.1 porting workflow and make adjustments to port between 4.2 and 5.0.

Result:
More automated PR porting between our branches.

Also fixes from issues identified with #16275

Motivation:
Following the success of #16273 we
should also have workflows for porting 4.2 -> 5.0, and 5.0 -> 4.2.

Modification:
Copy the 4.2 -> 4.1 porting workflow and make adjustments to port
between 4.2 and 5.0.

Result:
More automated PR porting between our branches.

Also fixes from issues identified with
#16275

(cherry picked from commit 6c611ec)
@chrisvest chrisvest enabled auto-merge (squash) February 17, 2026 18:28
@chrisvest chrisvest disabled auto-merge February 17, 2026 19:23
@chrisvest
Copy link
Copy Markdown
Member

chrisvest commented Feb 17, 2026

The build failures all look related to #16282. Merging.

@chrisvest chrisvest merged commit 52a8d4e into 5.0 Feb 17, 2026
8 of 13 checks passed
@chrisvest chrisvest deleted the forwardport-pr-16283-to-5.0 branch February 17, 2026 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants