Sorry for the noise. Lesson learned, lets not merge stuff onto existing renovate branches. I wasn't thinking and clicked the check box to rebase which blew away the changes. Then strangely github had popped a window on me that looked to merge the other commits back, I selected that which simply merged the 6.7.0 to master. I've reverted that and restored the branch as it was before this happened but prefixed as 'saved/'.

@JuditKnoll Can you please double check I didn't lose anything from #2446?

Sorry for the noise. Lesson learned, lets not merge stuff onto existing renovate branches. I wasn't thinking and clicked the check box to rebase which blew away the changes. Then strangely github had popped a window on me that looked to merge the other commits back, I selected that which simply merged the 6.7.0 to master. I've reverted that and restored the branch as it was before this happened but prefixed as 'saved/'.

@JuditKnoll Can you please double check I didn't lose anything from #2446?

Not a problem, everyone makes mistakes. Maybe we could document it somewhere (e.g. contribution guidelines) so even newcomers will know - originally I wasn't sure, since the change belongs to the renovate PR.
Checked it, everything seems good :) The only difference is the bcel version change, where we should be careful when merging this PR.

addressed, closing.