Skip to content

chore(deps): update go dependencies (major) - autoclosed #3502

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

chore(deps): update go dependencies (major) - autoclosed #3502

wants to merge 1 commit into from
+7 −7

Conversation

@red-hat-konflux
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Nov 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
github.com/MakeNowJust/heredoc v1.0.0 -> v2.0.1 age confidence
github.com/cenkalti/backoff/v4 v4.3.0 -> v5.0.3 age confidence
github.com/golang-jwt/jwt/v4 v4.5.2 -> v5.3.0 age confidence
github.com/onsi/ginkgo v1.16.5 -> v2.27.2 age confidence
go.yaml.in/yaml/v2 v2.4.3 -> v3.0.4 age confidence
gomodules.xyz/jsonpatch/v2 v2.4.0 -> v3.0.1 age confidence
gopkg.in/evanphx/json-patch.v4 v4.12.0 -> v5.9.11 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

Release Notes

MakeNowJust/heredoc (github.com/MakeNowJust/heredoc)

v2.0.1

Compare Source

Version 2.0.1

Fixes

  • Correct import path for Go modules

v2.0.0

Compare Source

Version 2.0.0

Breaking Changes

  • Treats only white space (U+0020) and horizontal tabs (U+000D) as space characters. (#​6)
cenkalti/backoff (github.com/cenkalti/backoff/v4)

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

golang-jwt/jwt (github.com/golang-jwt/jwt/v4)

v5.3.0

Compare Source

This release is almost identical to to v5.2.3 but now correctly indicates Go 1.21 as minimum requirement.

What's Changed

Full Changelog: golang-jwt/jwt@v5.2.3...v5.3.0

v5.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.2...v5.2.3

v5.2.2

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.1...v5.2.2

v5.2.1

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.2.0...v5.2.1

v5.2.0

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.1.0...v5.2.0

v5.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v5.0.0...v5.1.0

v5.0.0

Compare Source

🚀 New Major Version v5 🚀

It's finally here, the release you have been waiting for! We don't take breaking changes lightly, but the changes outlined below were necessary to address some of the challenges of the previous API. A big thanks for @​mfridman for all the reviews, all contributors for their commits and of course @​dgrijalva for the original code. I hope we kept some of the spirit of your original v4 branch alive in the approach we have taken here.
~@​oxisto, on behalf of @​golang-jwt/maintainers

Version v5 contains a major rework of core functionalities in the jwt-go library. This includes support for several validation options as well as a re-design of the Claims interface. Lastly, we reworked how errors work under the hood, which should provide a better overall developer experience.

Starting from v5.0.0, the import path will be:

"github.com/golang-jwt/jwt/v5"

For most users, changing the import path should suffice. However, since we intentionally changed and cleaned some of the public API, existing programs might need to be updated. The following sections describe significant changes and corresponding updates for existing programs.

Parsing and Validation Options

Under the hood, a new validator struct takes care of validating the claims. A long awaited feature has been the option to fine-tune the validation of tokens. This is now possible with several ParserOption functions that can be appended to most Parse functions, such as ParseWithClaims. The most important options and changes are:

  • Added WithLeeway to support specifying the leeway that is allowed when validating time-based claims, such as exp or nbf.
  • Changed default behavior to not check the iat claim. Usage of this claim is OPTIONAL according to the JWT RFC. The claim itself is also purely informational according to the RFC, so a strict validation failure is not recommended. If you want to check for sensible values in these claims, please use the WithIssuedAt parser option.
  • Added WithAudience, WithSubject and WithIssuer to support checking for expected aud, sub and iss.
  • Added WithStrictDecoding and WithPaddingAllowed options to allow previously global settings to enable base64 strict encoding and the parsing of base64 strings with padding. The latter is strictly speaking against the standard, but unfortunately some of the major identity providers issue some of these incorrect tokens. Both options are disabled by default.

Changes to the Claims interface

Complete Restructuring

Previously, the claims interface was satisfied with an implementation of a Valid() error function. This had several issues:

  • The different claim types (struct claims, map claims, etc.) then contained similar (but not 100 % identical) code of how this validation was done. This lead to a lot of (almost) duplicate code and was hard to maintain
  • It was not really semantically close to what a "claim" (or a set of claims) really is; which is a list of defined key/value pairs with a certain semantic meaning.

Since all the validation functionality is now extracted into the validator, all VerifyXXX and Valid functions have been removed from the Claims interface. Instead, the interface now represents a list of getters to retrieve values with a specific meaning. This allows us to completely decouple the validation logic with the underlying storage representation of the claim, which could be a struct, a map or even something stored in a database.

type Claims interface {
	GetExpirationTime() (*NumericDate, error)
	GetIssuedAt() (*NumericDate, error)
	GetNotBefore() (*NumericDate, error)
	GetIssuer() (string, error)
	GetSubject() (string, error)
	GetAudience() (ClaimStrings, error)
}
Supported Claim Types and Removal of StandardClaims

The two standard claim types supported by this library, MapClaims and RegisteredClaims both implement the necessary functions of this interface. The old StandardClaims struct, which has already been deprecated in v4 is now removed.

Users using custom claims, in most cases, will not experience any changes in the behavior as long as they embedded RegisteredClaims. If they created a new claim type from scratch, they now need to implemented the proper getter functions.

Migrating Application Specific Logic of the old Valid

Previously, users could override the Valid method in a custom claim, for example to extend the validation with application-specific claims. However, this was always very dangerous, since once could easily disable the standard validation and signature checking.

In order to avoid that, while still supporting the use-case, a new ClaimsValidator interface has been introduced. This interface consists of the Validate() error function. If the validator sees, that a Claims struct implements this interface, the errors returned to the Validate function will be appended to the regular standard validation. It is not possible to disable the standard validation anymore (even only by accident).

Usage examples can be found in example_test.go, to build claims structs like the following.

// MyCustomClaims includes all registered claims, plus Foo.
type MyCustomClaims struct {
	Foo string `json:"foo"`
	jwt.RegisteredClaims
}

// Validate can be used to execute additional application-specific claims
// validation.
func (m MyCustomClaims) Validate() error {
	if m.Foo != "bar" {
		return errors.New("must be foobar")
	}

	return nil
}

Changes to the Token and Parser struct

The previously global functions DecodeSegment and EncodeSegment were moved to the Parser and Token struct respectively. This will allow us in the future to configure the behavior of these two based on options supplied on the parser or the token (creation). This also removes two previously global variables and moves them to parser options WithStrictDecoding and WithPaddingAllowed.

In order to do that, we had to adjust the way signing methods work. Previously they were given a base64 encoded signature in Verify and were expected to return a base64 encoded version of the signature in Sign, both as a string. However, this made it necessary to have DecodeSegment and EncodeSegment global and was a less than perfect design because we were repeating encoding/decoding steps for all signing methods. Now, Sign and Verify operate on a decoded signature as a []byte, which feels more natural for a cryptographic operation anyway. Lastly, Parse and SignedString take care of the final encoding/decoding part.

In addition to that, we also changed the Signature field on Token from a string to []byte and this is also now populated with the decoded form. This is also more consistent, because the other parts of the JWT, mainly Header and Claims were already stored in decoded form in Token. Only the signature was stored in base64 encoded form, which was redundant with the information in the Raw field, which contains the complete token as base64.

type Token struct {
	Raw       string                 // Raw contains the raw token
	Method    SigningMethod          // Method is the signing method used or to be used
	Header    map[string]interface{} // Header is the first segment of the token in decoded form
	Claims    Claims                 // Claims is the second segment of the token in decoded form
	Signature []byte                 // Signature is the third segment of the token in decoded form
	Valid     bool                   // Valid specifies if the token is valid
}

Most (if not all) of these changes should not impact the normal usage of this library. Only users directly accessing the Signature field as well as developers of custom signing methods should be affected.

What's Changed

New Contributors

Full Changelog: golang-jwt/jwt@v4.5.0...v5.0.0

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

v2.27.2

Compare Source

2.27.2

Fixes
  • inline automaxprocs to simplify dependencies; this will be removed when Go 1.26 comes out [a69113a]
Maintenance
  • Fix syntax errors and typo [a99c6e0]
  • Fix paragraph position error [f993df5]

v2.27.1

Compare Source

2.27.1

Fixes
  • Fix Ginkgo Reporter slice-bounds panic [606c1cb]
  • Bug Fix: Add GinkoTBWrapper.Attr() and GinkoTBWrapper.Output() [a6463b3]

v2.27.0

Compare Source

2.27.0

Features
Transforming Nodes during Tree Construction

This release adds support for NodeArgsTransformers that can be registered with AddTreeConstructionNodeArgsTransformer.

These are called during the tree construction phase as nodes are constructed and can modify the node strings and decorators. This enables frameworks built on top of Ginkgo to modify Ginkgo nodes and enforce conventions.

Learn more here.

Spec Prioritization

A new SpecPriority(int) decorator has been added. Ginkgo will honor priority when ordering specs, ensuring that higher priority specs start running before lower priority specs

Learn more here.

Maintenance

v2.26.0

Compare Source

2.26.0

Features

Ginkgo can now generate json-formatted reports that are compatible with the go test json format. Use ginkgo --gojson-report=report.go.json. This is not intended to be a replacement for Ginkgo's native json format which is more information rich and better models Ginkgo's test structure semantics.

v2.25.3

Compare Source

2.25.3

Fixes
  • emit --github-output group only for progress report itself [f01aed1]

v2.25.2

Compare Source

2.25.2

Fixes

Add github output group for progress report content

Maintenance

Bump Gomega

v2.25.1

Compare Source

2.25.1

Fixes
  • fix(types): ignore nameless nodes on FullText() [10866d3]
  • chore: fix some CodeQL warnings [2e42cff]

v2.25.0

Compare Source

2.25.0

AroundNode

This release introduces a new decorator to support more complex spec setup usecases.

AroundNode registers a function that runs before each individual node. This is considered a more advanced decorator.

Please read the docs for more information and some examples.

Allowed signatures:

  • AroundNode(func()) - func will be called before the node is run.
  • AroundNode(func(ctx context.Context) context.Context) - func can wrap the passed in context and return a new one which will be passed on to the node.
  • AroundNode(func(ctx context.Context, body func(ctx context.Context))) - ctx is the context for the node and body is a function that must be called to run the node. This gives you complete control over what runs before and after the node.

Multiple AroundNode decorators can be applied to a single node and they will run in the order they are applied.

Unlike setup nodes like BeforeEach and DeferCleanup, AroundNode is guaranteed to run in the same goroutine as the decorated node. This is necessary when working with lower-level libraries that must run on a single thread (you can call runtime.LockOSThread() in the AroundNode to ensure that the node runs on a single thread).

Since AroundNode allows you to modify the context you can also use AroundNode to implement shared setup that attaches values to the context.

If applied to a container, AroundNode will run before every node in the container. Including setup nodes like BeforeEach and DeferCleanup.

AroundNode can also be applied to RunSpecs to run before every node in the suite. This opens up new mechanisms for instrumenting individual nodes across an entire suite.

v2.24.0

Compare Source

2.24.0

Features

Specs can now be decorated with (e.g.) SemVerConstraint("2.1.0") and ginkgo --sem-ver-filter="2.1.1" will only run constrained specs that match the requested version. Learn more in the docs here! Thanks to @​Icarus9913 for the PR.

Fixes
Maintenance

Numerous dependency bumps and documentation fixes

v2.23.4

Compare Source

2.23.4

Prior to this release Ginkgo would compute the incorrect number of available CPUs when running with -p in a linux container. Thanks to @​emirot for the fix!

Features
  • Add automaxprocs for using CPUQuota [2b9c428]
Fixes
  • clarify gotchas about -vet flag [1f59d07]
Maintenance

v2.23.3

Compare Source

2.23.3

Fixes
  • allow - as a standalone argument [cfcc1a5]
  • Bug Fix: Add GinkoTBWrapper.Chdir() and GinkoTBWrapper.Context() [feaf292]
  • ignore exit code for symbol test on linux [88e2282]

v2.23.2

Compare Source

2.23.2

🎉🎉🎉

At long last, some long-standing performance gaps between ginkgo and go test have been resolved!

Ginkgo operates by running go test -c to generate test binaries, and then running those binaries. It turns out that the compilation step of go test -c is slower than go test's compilation step because go test strips out debug symbols (ldflags=-w) whereas go test -c does not.

Ginkgo now passes the appropriate ldflags to go test -c when running specs to strip out symbols. This is only done when it is safe to do so and symbols are preferred when profiling is enabled and when ginkgo build is called explicitly.

This, coupled, with the instructions for disabling XProtect on MacOS yields a much better performance experience with Ginkgo.

v2.23.1

Compare Source

2.23.1

🚨 For users on MacOS 🚨

A long-standing Ginkgo performance issue on MacOS seems to be due to mac's antimalware XProtect. You can follow the instructions here to disable it in your terminal. Doing so sped up Ginkgo's own test suite from 1m8s to 47s.

Fixes

Ginkgo's CLI is now a bit clearer if you pass flags in incorrectly:

  • make it clearer that you need to pass a filename to the various profile flags, not an absolute directory [a0e52ff]
  • emit an error and exit if the ginkgo invocation includes flags after positional arguments [b799d8d]

This might cause existing CI builds to fail. If so then it's likely that your CI build was misconfigured and should be corrected. Open an issue if you need help.

v2.23.0

Compare Source

2.23.0

Ginkgo 2.23.0 adds a handful of methods to GinkgoT() to make it compatible with the testing.TB interface in Go 1.24. GinkgoT().Context(), in particular, is a useful shorthand for generating a new context that will clean itself up in a DeferCleanup(). This has subtle behavior differences from the golang implementation but should make sense in a Ginkgo... um... context.

Features
  • bump to go 1.24.0 - support new testing.TB methods and add a test to cover testing.TB regressions [37a511b]
Fixes
  • fix edge case where build -o is pointing at an explicit file, not a directory [7556a86]
  • Fix binary paths when precompiling multiple suites. [4df06c6]
Maintenance

v2.22.2

Compare Source

What's Changed

Full Changelog: onsi/ginkgo@v2.22.1...v2.22.2

v2.22.1

Compare Source

2.22.1

Fixes

Fix CSV encoding

Maintenance
  • ensure *.test files are gitignored so we don't accidentally commit compiled tests again [c88c634]
  • remove golang.org/x/net/context in favour of stdlib context [4df44bf]

v2.22.0

Compare Source

2.22.0

Features
  • Add label to serial nodes [0fcaa08]

This allows serial tests to be filtered using the label-filter

Maintenance

Various doc fixes

v2.21.0

Compare Source

2.21.0

Features
  • add support for GINKGO_TIME_FORMAT [a69eb39]
  • add GINKGO_NO_COLOR to disable colors via environment variables [bcab9c8]
Fixes
  • increase threshold in timeline matcher [e548367]
  • Fix the document by replacing SpecsThatWillBeRun with SpecsThatWillRun
    [c2c4d3c]
Maintenance
  • bump various dependencies [7e65a00]

v2.20.2

Compare Source

2.20.2

Require Go 1.22+

Maintenance

v2.20.1

Compare Source

2.20.1

Fixes
  • make BeSpecEvent duration matcher more forgiving [d6f9640]

v2.20.0

Compare Source

2.20.0

Features
Maintenance
  • Add update-deps to makefile [d303d14]
  • bump all dependencies [7a50221]

v2.19.1

Compare Source

2.19.1

Fixes
  • update supported platforms for race conditions [63c8c30]
  • [build] Allow custom name for binaries. [ff41e27]
Maintenance

v2.19.0

Compare Source

2.19.0

Features

Label Sets allow for more expressive and flexible label filtering.

v2.18.0

Compare Source

2.18.0

Features
  • Add --slience-skips and --force-newlines [f010b65]
  • fail when no tests were run and --fail-on-empty was set [d80eebe]
Fixes
  • Fix table entry context edge case [42013d6]
Maintenance

v2.17.3

Compare Source

2.17.3

Fixes

ginkgo watch now ignores hidden files [bde6e00]

v2.17.2

Compare Source

2.17.2

Fixes
  • fix: close files [32259c8]
  • fix github output log level for skipped specs [780e7a3]
Maintenance

v2.17.1

Compare Source

2.17.1

Fixes
  • If the user sets --seed=0, make sure all parallel nodes get the same seed [af0330d]

v2.17.0

Compare Source

2.17.0

Features
  • add --github-output for nicer output in github actions [e8a2056]
Maintenance

v2.16.0

Compare Source

2.16.0

Features
  • add SpecContext to reporting nodes
Fixes
Maintenance

v2.15.0

Compare Source

2.15.0

Features
  • JUnit reports now interpret Label(owner:X) and set owner to X. [8f3bd70]
  • include cancellation reason when cancelling spec context [96e915c]
Fixes
  • emit output of failed go tool cover invocation so users can try to debug things for themselves [c245d09]
  • fix outline when using nodot in ginkgo v2 [dca77c8]
  • Document areas where GinkgoT() behaves differently from testing.T [dbaf18f]
  • bugfix(docs): use Unsetenv instead of Clearenv (#​1337) [6f67a14]
Maintenance

v2.14.0

Compare Source

2.14.0

Features

You can now use GinkgoTB() when you need an instance of testing.TB to pass to a library.

Prior to this release table testing only supported generating individual Its for each test entry. DescribeTableSubtree extends table testing support to entire testing subtrees - under the hood DescrieTableSubtree generates a new container for each entry and invokes your function to fill our the container. See the docs to learn more.

Fixes
Maintenance

Configuration

📅 Schedule: 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.

This PR has been generated by MintMaker (powered by Renovate Bot).

@red-hat-konflux
chore(deps): update go dependencies
728428e 
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux
Copy link
Contributor Author

red-hat-konflux bot commented Nov 1, 2025

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: go get -t ./...
go: errors parsing go.mod:
go.mod:9:2: replace github.com/golang-jwt/jwt/v4: version "v5.3.0" invalid: should be v4, not v5
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod vendor' has not been added to the allowed list in allowedCommands
File name: go.mod
Post-upgrade command 'go mod verify' has not been added to the allowed list in allowedCommands

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 1, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux[bot]
Once this PR has been reviewed and has the lgtm label, please assign mansikulkarni96 for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

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

@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 1, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 05:03
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 05:05
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 1, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 1, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 09:17
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 09:18
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 1, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 1, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 12:34
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 1, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 12:35
@red-hat-konflux red-hat-konflux bot reopened this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 1, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 16:32
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 1, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 1, 2025 16:33
@red-hat-konflux red-hat-konflux bot reopened this Nov 1, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 1, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 4, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 4, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 5, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 00:31
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 5, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 00:35
@red-hat-konflux red-hat-konflux bot reopened this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 5, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 04:36
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 5, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 04:41
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 5, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 08:33
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 08:37
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 5, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 5, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 12:28
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) - autoclosed chore(deps): update go dependencies (major) Nov 5, 2025
@red-hat-konflux red-hat-konflux bot reopened this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot restored the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 12:33
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 5, 2025

@red-hat-konflux[bot]: The following tests 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/unit 728428e link true /test unit
ci/prow/lint 728428e link true /test lint
ci/prow/ci-bundle-wmco-bundle 728428e link true /test ci-bundle-wmco-bundle
ci/prow/nutanix-e2e-operator 728428e link true /test nutanix-e2e-operator
ci/prow/wicd-unit-vsphere 728428e link true /test wicd-unit-vsphere
ci/prow/aws-e2e-operator 728428e link true /test aws-e2e-operator
ci/prow/platform-none-vsphere-e2e-operator 728428e link true /test platform-none-vsphere-e2e-operator
ci/prow/vsphere-e2e-operator 728428e link true /test vsphere-e2e-operator
ci/prow/images 728428e link true /test images
ci/prow/azure-e2e-upgrade 728428e link true /test azure-e2e-upgrade
ci/prow/azure-e2e-operator 728428e link true /test azure-e2e-operator
ci/prow/vsphere-disconnected-e2e-operator 728428e link true /test vsphere-disconnected-e2e-operator
ci/prow/gcp-e2e-operator 728428e link true /test gcp-e2e-operator
ci/prow/vsphere-proxy-e2e-operator 728428e link true /test vsphere-proxy-e2e-operator

Full PR test history. Your PR dashboard.

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.

@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies (major) chore(deps): update go dependencies (major) - autoclosed Nov 5, 2025
@red-hat-konflux red-hat-konflux bot closed this Nov 5, 2025
@red-hat-konflux red-hat-konflux bot deleted the konflux/mintmaker/master/major-go-dependencies branch November 5, 2025 16:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mansikulkarni96 mansikulkarni96 Awaiting requested review from mansikulkarni96

@sebsoto sebsoto Awaiting requested review from sebsoto

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants