Could you open a PR against main as well? Otherwise we may regress if a new release is created from main and it doesn't have this update.

Update CDI dependency to v0.8.1. That pulls in a fix for a SIGSEGV/panic, which in principle could be triggered if we're out of file descriptors while we're instantiating the CDI cache.

Opened #11449. Sorry for the delay. I was meant to do it right after 2.0.x, but got caught up and then sidetracked by something else.

Thanks, and no worries! (Sorry for being pedantic; just have had the experience that we had a contributor opening a fix against a release branch, and we didn't notice, then ended up with a regression in the release after 🙈); GitHub makes it really easy to miss what branch a PR was opened against (we ended up with a rather hacky way to invalidate PRs if they don't mention the release branch in the title for that reason)

Thanks, and no worries! (Sorry for being pedantic; just have had the experience that we had a contributor opening a fix against a release branch, and we didn't notice, then ended up with a regression in the release after 🙈); GitHub makes it really easy to miss what branch a PR was opened against (we ended up with a rather hacky way to invalidate PRs if they don't mention the release branch in the title for that reason)

@thaJeztah No prob and no offense taken whatsoever. I agree that it is better to call out/remind in these cases just to be sure. Some folks get easily distracted and then forget things. And I am definitely one of those nowadays.