Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Oh there's another Windows related change that'd be nice to get into 1.6 also #7023

Is this still draft?

@AkihiroSuda Ideally I'd like to get in #7023 and backported, had almost forgot about it. It's kind of walking the line between "backportable" however. Some folks want it fixed, but I'm not sure if anyone actually relied on the behavior today that's altered in that change, so maybe it makes sense to just land in 1.7. I'd argue what happens today is a bug however

Sorry for the hold up here 😐 Like I mentioned I realized it'd be nice to get in another fix we had for Windows as it was fairly far along in review #7023. Fixed some feedback and it's been approved again so hopefully can get that checked in and cherry-picked to 1.6 and I'll rebase this

#7242 is merged

I'm not near a computer, but can we update go versions as well? There was a Go security release yesterday

@thaJeztah Sure. I'll open up against main, 1.6 and 1.5 and rebase after

Thank you! In case useful; it's mostly find&replace, but some branches have multiple go versions in CI. For me, especially the version used in the Dockerfiles is relevant, because our packaging script uses that version to automatically pick the Go version to use ☺️

Here's one of the previous bumps; #7159

@thaJeztah

Main: #7243
1.6: #7244
1.5: #7245

Okay, now that the Go bumps are in let me rebase, update the generated notes and add a blurb about the extra windows fix. Any other changes we need... going once... going twice... 😆

Should be ready to go, thanks for the patience