Backporting of PRs

[mcollina]

How do we want to backport PRs to v6.x to be included in Node.js v22 and v20?

@KhafraDev @Uzlopak I think you have done a few bugfixes, could you cherry-pick the commits into the v6.x branch?

Please add the backport v6.x label to automatically backport via actions (let's see if it works)

[metcoder95]

Beyond the bugfixes, do we know what else do we want to backport?

[mcollina]

I can see we might want to backport certain perf improvements or new features (like caching).

[metcoder95]

I'll start backporting some of the interceptors this weekend

[KhafraDev]

The only bug fix I can think of is e96178f, but since WebSocket internals were rewritten I can't rebase easily. I'll work on fixing it in a separate PR.

[Uzlopak]

I will backport my PRs today

[Uzlopak]

The backporting label seems to be unable to handle the changes properly?

[metcoder95]

As soon as it detects there are already overlapping changes on top of the commit (PR) you want to backport, and it can have conflicts, it fails. Tried with some of your PRs without success.
The ones that are cleaner goes smoothly

[Uzlopak]

I really want to backport the PRs but the suggested way is not working properly. Is it acceptable to "manually" backport?

[Uzlopak]

@mcollina

[mcollina]

yes of course!