Operator supported versions schedule

We're starting to install crdb in our cluster using the Operator. I see that the latest supported version is v22.2.2 which was superseded by 22.2.3 4 months ago. Since then there have been a further 5 patch releases.

I was wondering what the schedule/plan was for including updated versions in the support matrix for this operator? Looking through the PRs, I can't immediately see any strong cadence aside from the Github Action which checks for new releases and creates a PR. If this is not something done often or at a regular schedule, is it possible to override the forced support matrix? If we do not have a way to update patch increments as they are released, we will likely look to not use the operator, because being locked out of patch releases is not safe in production.