Zoran Regvart

> Hang on, test failed in this run: [helm/helm/actions/runs/7180014992/job/19656794257?pr=12310](https://github.com/helm/helm/actions/runs/7180014992/job/19656794257?pr=12310) Odd, I cannot reproduce that: go test ./... -run TestTLSRegistryClientTestSuite -v ? helm.sh/helm/v3/internal/test [no test files] ? helm.sh/helm/v3/internal/test/ensure [no test files]...

I is unclear to me what the expectation here is, i.e. could a release of Helm v4 be made with this or should the backward compatibility be maintained without exceptions....

See https://github.com/netlify/cli/issues/5977 and https://github.com/netlify/cli/pull/6362

I don't think this is the issue, I think the `og:image` should be an [absolute URL](https://ogp.me/#structured), which it currently is not.

Just noting my workaround which is to use `nul := base64.decode("AA==")`. I don't think many folk will run into this issue. I needed it for calculating a digest of a...

Would require that JUnit5 is used (I see JUnit 4 in a [number of places](https://github.com/search?q=repo%3Ahawtio%2Fhawtio%20junit-version&type=code)). The output when used looks like [this](https://github.com/zregvart/junit-github-reporter-example/pull/6/files) and [this](https://github.com/zregvart/junit-github-reporter-example/actions/runs/5573273744).

I see that AWX has a OpenAPI specification that [can be built](https://github.com/ansible/awx/blob/devel/CONTRIBUTING.md#building-api-documentation), perhaps the easiest way would be to build that specification and hand it over to the custom API...

Perhaps we can be more explicit for the `pr/handover` label, something like `pr/remove-to-merge`? And perhaps we can use `[ok to merge]` (or 👌 to be real hipsters) instead of `[handover]`?