From a4be83f4fd7c0652cd30398e3e94d643e2833dcc Mon Sep 17 00:00:00 2001 From: Peter Svensson Date: Thu, 7 May 2026 12:23:50 +0200 Subject: [PATCH] fix: keep gomega in go.sum across renovate updates `test/integration/{integration,operator}_test.go` import gomega behind the `//go:build integration` tag. `go mod tidy` ignores tagged files, so renovate-driven version bumps strip or omit gomega from go.sum, breaking the integration job (e.g. PR #132). Add a tag-free blank import in the same package so tidy keeps gomega tracked. The file has no runtime impact: under the integration tag it sits next to the real users; without the tag it builds alone with just the side-effect import. --- test/integration/deps_test.go | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 test/integration/deps_test.go diff --git a/test/integration/deps_test.go b/test/integration/deps_test.go new file mode 100644 index 0000000..eb57172 --- /dev/null +++ b/test/integration/deps_test.go @@ -0,0 +1,15 @@ +// Copyright 2025 OpzKit +// +// Licensed under the MIT License. +// See LICENSE file in the project root for full license information. + +// Imported here (without the integration build tag) so `go mod tidy` keeps +// ginkgo and gomega in go.sum. Real usages live in *_test.go files behind +// //go:build integration. + +package integration + +import ( + _ "github.com/onsi/ginkgo/v2" + _ "github.com/onsi/gomega" +)