OCM-00000 | ci: Update testing

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/onsi/ginkgo/v2	v2.27.2 → v2.32.0
github.com/onsi/gomega	v1.38.2 → v1.42.1
go.uber.org/mock	v0.4.0 → v0.6.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

onsi/ginkgo (github.com/onsi/ginkgo/v2)

v2.32.0

Compare Source

2.32.0

-fd generate RSpec-style documentation output. Thank @​woodie !
--sleep-on-failure pauses a failed spec before teardown. Thanks @​qinqon !

v2.31.0

Compare Source

2.31.0

Add a bunch of Claude Skills via the marketplace:

/plugin marketplace add onsi/ginkgo
/plugin install ginkgo@ginkgo

v2.30.0

Compare Source

2.30.0

Features

Ginkgo now allows extentions/global.Reset to support running multiple suites from within a single process. This may take some massaging on your part (see 1672) but can dramatically speed up codebases with O(hundreds) of test suites.

Thanks @​lawrencejones !

Fixes

• Fix nested --github-output group for progress report nested inside timeline [4f62d7a]

v2.29.0

Compare Source

2.29.0

GinkgoHelperGo makes it easier to write test helpers that need to run in goroutines. Specifically, it makes managing the failure state and capturing failure panics correctly straightforward.

ginkgo outline now includes entries defined in DescribeTableSubtree

v2.28.3

Compare Source

2.28.3

Maintenance

Bump all dependencies

v2.28.2

Compare Source

2.28.2

• Add ArtifactDir() to support Go 1.26 testing.TB interface [f3a36b6]
• Implement shell completion [94151c8]
• Add asan CLI option mirroring msan implementation [4d21dbb]
• Bump uri from 1.0.3 to 1.0.4 in /docs (#​1630) [c102161]
• fix aspect ratio [9619647]
• update logos [5779304]

v2.28.1

Compare Source

2.28.1

Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.

v2.28.0

Compare Source

2.28.0

Ginkgo's SemVer filter now supports filtering multiple components by SemVer version:

It("should work in a specific version range (1.0.0, 2.0.0) and third-party dependency redis in [8.0.0, ~)", SemVerConstraint(">= 3.2.0"), ComponentSemVerConstraint("redis", ">= 8.0.0") func() {
    // This test will only run when version is between 1.0.0 (exclusive) and 2.0.0 (exclusive) and redis version is >= 8.0.0
})

can be filtered in or out with an invocation like:

ginkgo --sem-ver-filter="2.1.1, redis=8.2.0"

Huge thanks to @​Icarus9913 for working on this!

v2.27.5

Compare Source

2.27.5

Fixes

Don't make a new formatter for each GinkgoT(); that's just silly and uses precious memory

v2.27.4

Compare Source

2.27.4

Fixes

• CurrentTreeConstructionNodeReport: fix for nested container nodes [59bc751]

v2.27.3

Compare Source

2.27.3

Fixes

report exit result in case of failure [1c9f356]
fix data race [ece19c8]

onsi/gomega (github.com/onsi/gomega)

v1.42.1

Compare Source

1.42.1

Bump Dependencies

v1.42.0

Compare Source

1.42.0

Add a set of Claude skill as a marketplace plugin

v1.41.0

Compare Source

v1.40.0

Compare Source

1.40.0

We're adopting a new release strategy to minimize dependency bloat in projects that consume Gomega. It is a limitation of the go mod toolchain that test subdependencies of your project's direct dependencies get pulled in as indirect dependencies. In the case of Gomega, this ends up pulling in all of Ginkgo into your go.mod even if you are only using Gomega (Gomega uses Ginkgo for its own tests).

Going forward, releases will strip out all tests, tidy up the go.mod and then push this stripped down version to a new master-lite branch. These stripped-down versions will receive the vx.y.z git tag and will be picked up by the go toolchain.

Please open an issue if this new release process causes unexpected changes for your projects.

v1.39.1

Compare Source

1.39.1

Update all dependencies. This auto-updated the required version of Go to 1.24, consistent with the fact that Go 1.23 has been out of support for almost six months.

v1.39.0

Compare Source

1.39.0

Features

Add MatchErrorStrictly which only passes if errors.Is(actual, expected) returns true. MatchError, by contrast, will fallback to string comparison.

v1.38.3

Compare Source

1.38.3

Fixes

make string formatitng more consistent for users who use format.Object directly

uber/mock (go.uber.org/mock)

v0.6.0

Compare Source

0.6.0 (18 Aug 2025)

Added

• #​258: Archive mode: a new mockgen mode that generates mocks out of archive files.

Fixed

• #​276: Fixed mockgen errors with go1.25 due to outdated golang.org/x/tools dependency.

v0.5.2

Compare Source

0.5.2 (28 Apr 2025)

Fixed

• #​248: Fixed an issue with type aliases not being included in generated code correctly.

v0.5.1

Compare Source

0.5.1 (7 Apr 2025)

Fixed

• #​220: Package mode will now generate code that uses aliases of types
  when they are used in the source.
• #​219: Fixed a collision between function argument names and package names
  in generated code.
• #​165: Fixed an issue where aliases specified by -imports were not being
  respected in generated code.

Thanks to @​mtoader and @​bstncartwright for their contributions to this release.

v0.5.0

Compare Source

0.5.0 (15 Oct 2024)

Added

• #​153: Add --write_command_comment flag to specify whether to include
  Generated by this command comment.
• #​191: Add --build_constraint flag to add //go:build directives
  to generated mocks
• #​214: Add gob mode to support custom package loading techniques in place
  of --exec_only

Changed

• #​181: Made mockgen faster by changing flags passed to go list.
• #​183: Made Cond matcher generic.
• #​204: Removed ISGOMOCK() from generated mocks.
• #​207: Deprecated reflect mode and replaced it with the new package mode.

Fixed

• #​144: Fix a deadlock that can happen when mocking an interface that
  matches fmt.Stringer.
• #​168: Fix an issue where the "generated by" comment was being included
  in the package comment of generated mocks.

Thanks to @​tulzke @​JacobOaks @​ARR4N @​sashamelentyev @​sywhang @​fasmat
@​eyasy1217 @​ghouscht @​tie @​Neo2308 @​carson-brill @​alexandear @​sodul
@​nbgraham for their contributions this release.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[red-hat-konflux]

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 9 additional dependencies were updated

Details:

Package	Change
golang.org/x/mod	v0.30.0 -> v0.36.0
golang.org/x/sync	v0.19.0 -> v0.21.0
github.com/google/pprof	v0.0.0-20250403155104-27863c87afa6 -> v0.0.0-20260402051712-545e8a4df936
golang.org/x/crypto	v0.46.0 -> v0.53.0
golang.org/x/net	v0.48.0 -> v0.56.0
golang.org/x/sys	v0.39.0 -> v0.46.0
golang.org/x/term	v0.38.0 -> v0.44.0
golang.org/x/text	v0.32.0 -> v0.38.0
golang.org/x/tools	v0.39.0 -> v0.45.0

[coderabbitai]

📝 Walkthrough

Walkthrough

The change updates dependency versions in go.mod, including github.com/onsi/ginkgo/v2, github.com/onsi/gomega, github.com/google/pprof, and several golang.org/x modules. It also removes the explicit go.uber.org/mock requirement from .bingo/mockgen.mod.

🚥 Pre-merge checks | ✅ 14 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is a Renovate dependency list and release notes, but it omits the repository's required summary, issue, testing, and checklist sections.	Rewrite the description using the required template, including PR Summary, issue context, type of change, validation steps, and checklist items.

✅ Passed checks (14 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and matches the PR's dependency/testing update theme.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	Only go.mod and .bingo/mockgen.mod changed; neither contains Ginkgo test titles or dynamic test-name strings.
Test Structure And Quality	✅ Passed	PR only updates dependency manifests (go.mod, .bingo/mockgen.mod); no Ginkgo test blocks or cluster-interacting test code changed, so the test-quality checks don't apply.
Microshift Test Compatibility	✅ Passed	Only Go module files changed; no new It/Describe test code or MicroShift-unsupported API usage was added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Only go.mod and .bingo/mockgen.mod changed; no test sources or new Ginkgo e2e specs were added, so the SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility	✅ Passed	Only module/vendor files changed; no deployment manifests, operator code, or controllers were modified, so no topology-sensitive scheduling logic was introduced.
Ote Binary Stdout Contract	✅ Passed	Diff only bumps vendored deps; no new stdout writes appear in main/init/TestMain/RunSpecs setup. The added completion code is outside the flagged entrypoint blocks.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Only dependency module files changed; no new or modified Ginkgo e2e tests or network code were introduced.
No-Weak-Crypto	✅ Passed	No changed hunk introduces MD5/SHA1/DES/RC4/3DES/ECB or custom/non-constant-time secret comparison; the weak-crypto names found were existing/vendor metadata only.
Container-Privileges	✅ Passed	PR only changes go.mod and .bingo/mockgen.mod; no container/K8s manifests were modified and no privilege settings were introduced.
No-Sensitive-Data-In-Logs	✅ Passed	Only dependency manifests changed (go.mod and .bingo/mockgen.mod); no logging code or sensitive data exposure was introduced.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch konflux/mintmaker/master/testing

---

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 26.17%. Comparing base (80fd9fb) to head (78317e4).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #3293   +/-   ##
=======================================
  Coverage   26.17%   26.17%           
=======================================
  Files         334      334           
  Lines       36704    36704           
=======================================
  Hits         9608     9608           
  Misses      26359    26359           
  Partials      737      737           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[amandahla]

/approve
/lgtm
/check-required-labels

[amandahla]

/test Red Hat Konflux / rosa-on-pull-request

[openshift-ci]

@amandahla: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test build

/test commits

/test coverage

/test e2e-presubmits-images

/test images-images

/test images-release-images

/test lint

/test test

The following commands are available to trigger optional jobs:

/test e2e-presubmits-pr-rosa-hcp-advanced

/test e2e-presubmits-pr-rosa-hcp-arm

/test e2e-presubmits-pr-rosa-hcp-private-link

/test e2e-presubmits-pr-rosa-shared-vpc

/test e2e-presubmits-pr-rosa-sts-advanced

/test e2e-presubmits-pr-rosa-sts-private-link

/test e2e-presubmits-pr-rosa-sts-shared-vpc

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-rosa-master-build

pull-ci-openshift-rosa-master-commits

pull-ci-openshift-rosa-master-coverage

pull-ci-openshift-rosa-master-e2e-presubmits-images

pull-ci-openshift-rosa-master-images-images

pull-ci-openshift-rosa-master-images-release-images

pull-ci-openshift-rosa-master-lint

pull-ci-openshift-rosa-master-test

Details

In response to this:

/test Red Hat Konflux / rosa-on-pull-request

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[amandahla]

/test rosa-on-pull-request

[openshift-ci]

@amandahla: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test build

/test commits

/test coverage

/test e2e-presubmits-images

/test images-images

/test images-release-images

/test lint

/test test

The following commands are available to trigger optional jobs:

/test e2e-presubmits-pr-rosa-hcp-advanced

/test e2e-presubmits-pr-rosa-hcp-arm

/test e2e-presubmits-pr-rosa-hcp-private-link

/test e2e-presubmits-pr-rosa-shared-vpc

/test e2e-presubmits-pr-rosa-sts-advanced

/test e2e-presubmits-pr-rosa-sts-private-link

/test e2e-presubmits-pr-rosa-sts-shared-vpc

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-rosa-master-build

pull-ci-openshift-rosa-master-commits

pull-ci-openshift-rosa-master-coverage

pull-ci-openshift-rosa-master-e2e-presubmits-images

pull-ci-openshift-rosa-master-images-images

pull-ci-openshift-rosa-master-images-release-images

pull-ci-openshift-rosa-master-lint

pull-ci-openshift-rosa-master-test

Details

In response to this:

/test rosa-on-pull-request

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci]

@red-hat-konflux[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/lint	092d0c9	link	true	/test lint

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[olucasfreitas]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amandahla, olucasfreitas, red-hat-konflux[bot]

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [amandahla,olucasfreitas]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment