Closed grokspawn closed 2 weeks ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 38.23%. Comparing base (
f279c4c
) to head (9d9c45c
). Report is 1 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
/lgtm cancel /approve cancel
@grokspawn
It seems that we have an issue to build it
Run hack/scripts/check-go-version.sh "4d6327f8d20e6a22c310b8ccae69e2eec63bd0a7" Found golang version: 1.22.5 ./.bingo/go.mod: Skipping, no version found ./.bingo/ginkgo.mod: 1.22.0: Updated golang version from 1.22 Error: Process completed with exit code 1.
See the CI: https://github.com/operator-framework/catalogd/actions/runs/11806891013/job/32892465153?pr=456
/approve cancel
/lgtm cancel /approve cancel
@grokspawn
It seems that we have an issue to build it
Run hack/scripts/check-go-version.sh "4d6327f8d20e6a22c310b8ccae69e2eec63bd0a7" Found golang version: 1.22.5 ./.bingo/go.mod: Skipping, no version found ./.bingo/ginkgo.mod: 1.22.0: Updated golang version from 1.22 Error: Process completed with exit code 1.
See the CI: https://github.com/operator-framework/catalogd/actions/runs/11806891013/job/32892465153?pr=456
This is not required CI, and it looks like the script isn't happy about how bingo represented the go version with the third octet (1.22.0) whereas that is correct. But there's no actual error here.
go-verdiff fixed by #458
This bumps ginkgo to 2.21.0 since dependabot does not bump go.mod and .bingo/* dependencies in the same PR.