New versions of grpc_health_probe not used in latest release image

[griffindvs]

Based on the registry.Dockerfile, it appears like the opm image should use a version of the grpc_health_probe that matches the version included in the go.mod:
https://github.com/operator-framework/operator-registry/blob/v1.55.0/registry.Dockerfile#L8-L10

It does not appear like this is picking up the correct version. The go.mod for v1.55.0 references grpc_health_probe v0.4.38: https://github.com/operator-framework/operator-registry/blob/v1.55.0/go.mod#L21

If we look inside the v1.55.0 image we see a different version reported:

podman run -it --entrypoint=sh quay.io/operator-framework/opm:v1.55.0
~ $ /bin/grpc_health_probe --version
${GITHUB_REF_NAME#v}; commit c500e0d74f5444f4643ec1d2499208da23d2e3cc

This commit: grpc-ecosystem/grpc-health-probe@c500e0d corresponds to the v0.4.37 tag of the health probe: https://github.com/grpc-ecosystem/grpc-health-probe/releases/tag/v0.4.37

[igormpmartins]

Is there any plans for updating grpc health probe? I ended up manually overriding grpc-health-probe in my images, as v0.4.37 has some security issues.

p.s.: v0.4.3.39 is already available.

[github-actions]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.