Skip to content

chore(deps): update go dependencies to v1 (major)#492

Open
red-hat-konflux[bot] wants to merge 1 commit intorelease-1.3from
konflux/mintmaker/release-1.3/major-go-deps
Open

chore(deps): update go dependencies to v1 (major)#492
red-hat-konflux[bot] wants to merge 1 commit intorelease-1.3from
konflux/mintmaker/release-1.3/major-go-deps

Conversation

@red-hat-konflux
Copy link

@red-hat-konflux red-hat-konflux bot commented Jan 13, 2026 •
edited
Loading

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change
github.com/ProtonMail/go-crypto indirect major v0.0.0-20230923063757-afb1ddc0824c -> v1.3.0
github.com/golang/snappy indirect major v0.0.4 -> v1.0.0
github.com/imdario/mergo indirect major v0.3.16 -> v1.0.2
github.com/sigstore/sigstore-go require major v0.7.2 -> v1.1.4
gitlab.com/gitlab-org/api/client-go require major v0.128.0 -> v1.23.0

Warning

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

Release Notes

ProtonMail/go-crypto (github.com/ProtonMail/go-crypto)

v1.3.0

Compare Source

What's Changed

  • API v2: Tolerate invalid key signatures if one verifies in #​284
  • Enforce acceptable hash functions in clearsign in #​281
  • Allow to set a decompressed message size limit in #​285
  • API v1: Only allow acceptable hashes when writing signatures in #​286

Full Changelog: ProtonMail/go-crypto@v1.2.0...v1.3.0

v1.3.0-proton

Compare Source

This release is v1.3.0 with support for the following non-standardized features:

v1.2.0

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.6...v1.2.0

v1.2.0-proton

Compare Source

What's Changed

This release is v1.2.0 with support for the following non-standardized features:

v1.1.6

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.5...v1.1.6

v1.1.6-proton

Compare Source

What's Changed

This release is v1.1.6 with support for the following non-standardized features:

v1.1.5

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.4...v1.1.5

v1.1.5-proton

Compare Source

What's Changed

This release is v1.1.5 with support for the following non-standardized features:

v1.1.4

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.3...v1.1.4

v1.1.4-proton

Compare Source

What's Changed

This release is v1.1.4 with support for the following non-standardized features:

v1.1.3

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.2...v1.1.3

v1.1.3-proton.2

Compare Source

What's Changed

This release is v1.1.3 with support for the following non-standardized features:

Patches v1.1.3-proton.1:

  • Update PQC ML-KEM key combiner to latest draft version.

v1.1.3-proton.1

Compare Source

What's Changed

This release is v1.1.3 with support for the following non-standardized features:

Patches v1.1.3-proton:

  • Marked forwarding key should not be usable in encryption.

v1.1.3-proton

Compare Source

What's Changed

This release is v1.1.3 with support for the following non-standardized features:

v1.1.2

Compare Source

What's Changed

  • Cleartext Framework: Exclude the line-ending separator when decoding plaintext by @​lubux in #​242

Full Changelog: ProtonMail/go-crypto@v1.1.1...v1.1.2

v1.1.2-proton

Compare Source

What's Changed

This release is v1.1.2 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.1

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.0...v1.1.1

v1.1.1-proton

Compare Source

What's Changed

This release is v1.1.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0

Compare Source

What's Changed

This release adds full support for the new version of the OpenPGP standard, RFC 9580. In addition, the release introduces an improved non-backwards compatible v2 API. The API in the openpgp package remains fully backwards compatible while the new v2 API is located in a separate v2 package in openpgp.

For the full changes since v1.0.0, see the previous release notes. For the full changelog, see ProtonMail/go-crypto@v1.0.0...v1.1.0.

Changes since v1.1.0-beta.0:

  • Replace expiring curve448 integration test vector by @​lubux
  • Validate input key size in SEIPDv2 decryption by @​lubux

Changelog since v1.1.0-beta.0: ProtonMail/go-crypto@v1.1.0-beta.0...v1.1.0.

v1.1.0-proton

Compare Source

What's Changed

This release is v1.1.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-beta.0-proton

Compare Source

This pre-release is v1.1.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-beta.0

Compare Source

What's Changed

Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.5...v1.1.0-beta.0

v1.1.0-alpha.5-proton

Compare Source

This pre-release is v1.1.0-alpha.5 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.5

Compare Source

What's Changed

  • Accept both encryption key flags for encryption/decryption (#​217)
  • [v2] Check signature details of binding signatures (#​218)

Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.4...v1.1.0-alpha.5

v1.1.0-alpha.4-proton

Compare Source

This pre-release is v1.1.0-alpha.4 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.4

Compare Source

What's Changed

  • ECDH with v6 must use the full fingerprint (#​211)
  • Restrict S2K types (#​213)
  • Put support for reading v5 packets behind a feature flag (#​212)
  • Allow empty Key Flags subpackets (#​214)
  • Randomize v4 and v5 signatures via custom notation (#​209)
  • Fix SEIPDv2 packet parsing error messages (#​215)

Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.3...v1.1.0-alpha.4

v1.1.0-alpha.3-proton

Compare Source

This pre-release is v1.1.0-alpha.3 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.3

Compare Source

What's Changed

  • New functions to verify signature hash tags
  • Allow parsing certifications explicitly marked as exportable
  • Sorting signature sub-packets by their ID when serializing
  • Mark creation time, issuer key ID, and key flag signature sub-packets as critical
  • When AEAD is in use, the session key length is now determined by the cipher specified in the AEAD preference.

Full Changelog: v1.1.0-alpha.2...v1.1.0-alpha.3

v1.1.0-alpha.2-proton

Compare Source

v1.1.0-alpha.2

Compare Source

v1.1.0-alpha.1-proton

Compare Source

This pre-release is v1.1.0-alpha.1 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.1

Compare Source

What's Changed

Removes the openpgp.VerifyDetachedSignatureAndSaltedHash function and the packet.SaltedHashSpecifier as they are no longer required. They were introduced for verifying the headers in cleartext messages. However, in the latest crypto-refresh specification, cleartext message headers were dropped.

Full Changelog: v1.1.0-alpha.0...v1.1.0-alpha.1

v1.1.0-alpha.0-proton

Compare Source

This pre-release is v1.1.0-alpha.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-alpha.0

Compare Source

What's Changed

This major pre-release adds full support for the OpenPGP crypto refresh. In addition, the pre-release introduces an improved non-backwards compatible v2 API. The API in the openpgp package remains fully backwards compatible while the new v2 API is located in a separate v2 package in openpgp.

Full Changelog: v1.0.0...v1.1.0-alpha.0

V2 API

Import

The v2 API can be imported as:

openpgp ProtonMail/go-crypto/openpgp/v2
V2 API Breaking Changes

openpgp.v2.Entity struct fields have changed:

  • SelfSignature *packet.Signature removed
  • Signatures []*packet.Signature removed
  • DirectSignatures []*packet.VerifiableSignature added
  • Revocations []*packet.VerifiableSignature changed type

Methods of openpgp.v2.Entity that changed:

  • PrimaryIdentity(date time.Time) now requires a time argument.
  • EncryptionKey(date time.Time, config *packet.Config) now requires a new config argument.
  • CertificationKey(date time.Time, config *packet.Config) now requires a new config argument.
  • CertificationKeyById(date time.Time, id uint64, config *packet.Config) now requires a new config argument.
  • SigningKey(date time.Time, config *packet.Config) now requires a new config argument.
  • SigningKeyById(date time.Time, id uint64, config *packet.Config) now requires a new config argument.
  • Revoke(reason packet.ReasonForRevocation, reasonText string, config *packet.Config) is renamed to RevokeKey.

Removed methods of openpgp.v2.Entity:

  • RevokeSubkey(...) is replaced by (Subkey).Revoke(...)

openpgp.v2.Subkey struct fields have changed:

  • Sig *packet.Signature removed
  • Bindings []*packet.VerifiableSignature added
  • Primary *Entity added, pointing to the primary key.
  • Revocations []*packet.VerifiableSignature changed type

Methods of openpgp.v2.Subkey that changed:

  • Revoked(selfCertification *packet.Signature, date time.Time) now requires a selfCertification argument.

openpgp.v2.Identity struct fields have changed:

  • SelfSignature *packet.Signature removed
  • Signatures []*packet.Signature removed
  • SelfCertifications []*packet.VerifiableSignature added
  • OtherCertifications []*packet.VerifiableSignature added
  • Primary *Entity added, pointing to the primary key.
  • Revocations []*packet.VerifiableSignature changed type

Methods of openpgp.v2.Identity that changed:

  • Revoked(selfCertification *packet.Signature, date time.Time) now requires a selfCertification argument.

openpgp.v2.Key struct fields have changed:

  • PrimarySelfSignature *packet.Signature added, pointing to the selected self signature of the primary key.
  • Revocations []*packet.VerifiableSignature changed type

Interface openpgp.v2.KeyRing has changed:

  • KeysByIdUsage(...) removed
  • DecryptionKeys(...) removed
  • EntitiesById(id uint64) []*Entity added. This is the main internal method to access keys from the keyring now.

openpgp.v2.FileHints struct field has changed:

  • IsBinary removed and IsUTF8 added

API changes in openpgp.v2 for reading messages:

  • VerifyDetachedSignatureAndHash(...) removed; headers in clearsigned messages are no longer checked.
  • VerifyDetachedSignatureAndSaltedHash(...) removed
  • CheckDetachedSignature(...) removed; call VerifyDetachedSignature(...) instead
  • CheckDetachedSignatureAndSaltedHash(...) removed
  • CheckDetachedSignatureAndHash(...) removed
  • CheckArmoredDetachedSignature removed; call VerifyArmoredDetachedSignature instead

API changes in openpgp.v2 for writing messages:

  • DetachSign(..., signers []*Entity,...) now requires a slice of entities instead of a single entity as an argument.
  • ArmoredDetachSign(..., signers []*Entity,..., , params *SignParams) now requires a slice of entities instead of a single entity as an argument and replaces arguments with a SignParams object.
  • DetachSignText(..., signers []*Entity,...) now requires a slice of entities instead of a single entity as an argument.
  • ArmoredDetachSignText(..., signers []*Entity,...) now requires a slice of entities instead of a single entity as an argument.
  • EncryptText(...) removed; call EncryptWithParams(...) instead
  • EncryptSplit(...) removed; call EncryptWithParams(...) instead
  • EncryptTextSplit(...) removed; call EncryptWithParams(...) instead
  • Encrypt(..., toHidden []*Entity, signers []*Entity) now takes an additional toHidden recipients argument and requires a slice of signer entities instead of a single entity as an argument.
  • Sign(..., signers []*Entity,...) now requires a slice of entities instead of a single entity as an argument.
Features
Intended Recipients

Version 2 of the ProtonMail/go-crypto library introduces a feature for including the recipients' key fingerprints in signatures during message encryption. When encrypting and signing a message, the intended recipients are automatically included in the signature unless specifically hidden (i.e., hidden recipients). During the decryption process, if the signature contains intended recipients and the appropriate configuration flag is set, the library verifies whether the primary ID of the decryption key is present in the recipient list. This check can be disabled in the config when a hidden recipient decrypts the message.

Multi-signature Support

In previous iterations of ProtonMail/go-crypto, only a single signature creation and verification were supported in a PGP message. However, in Version 2, the library introduces the ability to sign messages with multiple signatures using different keys, such as a v4 and a v6 key. The encryption and signing methods now accept multiple signing keys as arguments, with each key designated for a specific signature. When reading PGP messages with Version 2, the library maintains an internal state for each known signature and verifies all of them within the message. To facilitate this functionality, the message details struct includes a new field that stores the verification state for each signature. A message is considered valid if at least one of the signatures successfully validates without any errors. For callers, the process of checking for signature errors remains similar to previous versions. However, if the caller requires the verification state of all signatures, they can utilize the new field in the message details struct.

Rework of How Signatures in Keys and Signatures

are Verified

In previous iterations of ProtonMail/go-crypto, key verification occurred during import based on the current time, while signature verification did not involve further key checks. However, this approach had limitations, as invalid keys could have been valid at the time of signature creation and mistakenly considered invalid. Version 2 changes how and when signatures are verified in keys (i.e., direct-signatures, self-signatures of userids, binding signatures in subkeys, revocations, etc). Unlike before, key signature verification no longer takes place during parsing. Instead, keys are now validated when they are utilized, following a similar approach to key handling in OpenPGP.js. Additionally, all signatures and expirations are validated to adhere to the key lifecycle outlined in the RFC. The validity of keys can now be checked at different points in time, leading to the following specific modifications:

  • During entity parsing, key validity is not checked.
  • When used for encryption or signing, keys are verified using the current time during the writing process.
  • During reading, the library verifies that each verification key was valid at the time of signature creation.
  • A clear separation is maintained between Entity, Subkey, Identity, and their respective validation methods.
  • Signature verification results are cached and reused to optimize computation. Further, version 2 includes various small improvements to increase the robustness of the key parsing functions.
Weak Algorithm Rejection

Version 2 introduces the option to specify weak algorithms for signatures in the config. Signatures that use weak algorithms are considered invalid.

Optional Packet Sequence Checker

Version 2 introduces a new feature that enables the validation of packet sequences in PGP messages. This functionality can be enabled in the config struct. In particular, it implements the pushdown automata (PDA) from PGPainless, developed by Paul Schaub. By leveraging this feature, users can ensure that the packet sequences in their PGP messages are valid and comply with the required structure. This addition further enhances the overall reliability and security of PGP message handling in Version 2.

Session Key Encryption and Decryption

Version 2 allows advanced users to retrieve the session key while encrypting a message by setting the respective flag in the config. In decryption, a caller can provide a session key that should be used for decryption.

Unify Write/Read API

Version 2 improves the compatibility between different APIs to allow combinations. The DetachSign function requires the caller to provide a Reader for the message, while encrypt returns a WriteCloser to which the message is written. The new version adds a function DetachSignWriter, which returns a WriteCloser similar to the encryption API. On the reading side, the verify detached signature API now relies on the same signature verification logic as the other read functions. Additionally, a new VerifyDetachedSignatureReader method similar to the ReadMessage API is introduced. It returns a message details struct that once read verifies the signature. Allows chaining different readers from the API, for example, to have a streaming API for encrypted detached signatures.

Params Struct as a Function Argument in the Write API

With the inclusion of new features, the write functions in go-crypto experienced significant growth in numbers. Each combination has its dedicated function. Version 2 introduces an EncryptWithParams/SignWithParams function that takes an EncryptParams/SignParams struct as an argument. The struct allows configuring the different features. This approach effectively reduces the number of API methods and simplifies the process of adding new features while maintaining compatibility with previous versions.

Others
  • Disable armor checksum on default armor.Encode method
  • Make unarmor more robust to empty header values
  • Allow key generation of v6 keys without an Identity
  • Allow compression in inline signed messages
  • Consider key preferences in detached signatures
  • Only compare time at a second granularity
  • Signal if the tag is not verified on close in AEAD decryption
  • Ensure that critical unknown packet tags result in message rejection
  • Ensure that decompression streams are closed and that the packet is completely read
  • Ensure that entity parsing does not reject keys with unknown subkeys
  • Check for known curves early when parsing ECDSA and ECDH keys
  • Skip signatures with the wrong type while parsing an entity
  • Support for signatures that appear in front of the data
  • Change file hints field IsBinary to IsUTF8

v1.0.0: Initial release

Compare Source

First tagged release.

golang/snappy (github.com/golang/snappy)

v1.0.0

Compare Source

Latest stable version, as of March 2025.

imdario/mergo (github.com/imdario/mergo)

v1.0.2

Compare Source

What's Changed

  • Drops gopkg.in/yaml.v3, only used for loading fixtures. Thanks @​trim21 for bringing to my attention (#​262) that this library is no longer maintained.

Full Changelog: darccio/mergo@v1.0.1...v1.0.2

v1.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: darccio/mergo@v1.0.0...v1.0.1

v1.0.0: 1.0.0 released with new module URL: dario.cat/mergo

Compare Source

This PR is a release containing 0.3.15 features but changing the module URL to dario.cat/mergo.

What's Changed

Full Changelog: darccio/mergo@v0.3.16...v1.0.0

sigstore/sigstore-go (github.com/sigstore/sigstore-go)

v1.1.4

Compare Source

What's Changed

  • Update rekor-tiles version path in #​531
  • Bump production Sigstore TUF root to latest in #​537
  • Bump staging Sigstore TUF root to latest in #​538
  • Bump deps for sigstore libraries in #​543

Full Changelog: sigstore/sigstore-go@v1.1.3...v1.1.4

v1.1.3

Compare Source

What's Changed

  • Set user agent for TUF and Rekor v2 clients in #​525

Full Changelog: sigstore/sigstore-go@v1.1.2...v1.1.3

v1.1.2

Compare Source

What's Changed

  • Allow no timestamps to be provided when verifying a key in #​510
  • Support other key algorithms for Rekor v2 in #​520

Full Changelog: sigstore/sigstore-go@v1.1.1...v1.1.2

v1.1.1

Compare Source

What's Changed

  • Make conformance compatible with rekor v2 in #​505
  • Update GetSigningConfig to use signing_config.v0.2.json in #​506
  • Refactor SelectService to return Service rather than URL, add supported API versions in #​503
  • Remove noisy log message in #​507

Full Changelog: sigstore/sigstore-go@v1.1.0...v1.1.1

v1.1.0

Compare Source

sigstore-go v1.1.0 introduces support for Rekor v2, a redesigned and modernized transparency log that's cheaper to operate, easier to scale, and simpler to maintain.

What's Changed

Full Changelog: sigstore/sigstore-go@v1.0.0...v1.1.0

v1.0.0

Compare Source

We're very excited to release sigstore-go 1.0! View the blog post announcing this release for more details.

This release should contain the last set of breaking changes until version 2.0, including a few renames (such as SignedEntityVerifier -> Verifier and VerifyTimestampAuthority -> VerifySignedTimestamp). We are excited to begin a new phase of simple, stable APIs!

What's Changed

Full Changelog: sigstore/sigstore-go@v0.7.3...v1.0.0

v0.7.3

Compare Source

Note: v0.7.3 will likely be the last release before v1.0.

What's Changed

Full Changelog: sigstore/sigstore-go@v0.7.2...v0.7.3

gitlab-org/api/client-go (gitlab.com/gitlab-org/api/client-go)

v1.23.0

Compare Source

1.23.0

🚀 Features
🔄 Other Changes

1.23.0 (2026-01-28)

Features
  • add group protected branches service (c7ffe6f)

v1.22.1

Compare Source

1.22.1

🐛 Bug Fixes
  • fix: Type Mismatch in UpdateSettingsOptions for SentryEnabled (!2690) by Zubeen
🔄 Other Changes
  • fix: URL tags for throttle protected path settings in UpdateSettingsOptions (!2705) by Zubeen
  • test: Refactor tests to use testify assertions 7 (!2700) by Zubeen
  • test: Refactor tests to use testify assertions 4 (!2696) by Zubeen
  • test: Refactor tests to use testify assertions 3 (!2695) by Zubeen
  • test(no-release): Refactor tests to use testify assertions 2 (!2694) by Zubeen
  • test(no-release): Refactor tests to use testify assertions (!2693) by Zubeen
  • test(no-release): Refactor tests to use testify assertions 6 (!2699) by Zubeen

1.22.1 (2026-01-28)

Bug Fixes
  • Type Mismatch in UpdateSettingsOptions for SentryEnabled (c2d3ca9)
  • URL tags for throttle protected path settings in UpdateSettingsOptions (a4a525d)

v1.22.0

Compare Source

1.22.0

🚀 Features
🔄 Other Changes
  • test: Refactor tests to use testify assertions 5 (!2697) by Zubeen

1.22.0 (2026-01-28)

Features
  • project_mirror: add ForceSyncProjectMirror (b13fcb7)

v1.21.0

Compare Source

1.21.0

🚀 Features
  • feat(settings): Add AnonymousSearchesAllowed field support (!2678) by Seif Hatem
🔄 Other Changes
  • feat: improve URL validation and error handling in client initialization (!2656) by Amer Khaled

1.21.0 (2026-01-27)

Features
  • improve URL validation and error handling in client initialization (9417155)
  • settings: Add AnonymousSearchesAllowed field support (7185888)

v1.20.0

Compare Source

1.20.0

🚀 Features
🔄 Other Changes

1.20.0 (2026-01-27)

Features

v1.19.0

Compare Source

1.19.0

🚀 Features
🔄 Other Changes

1.19.0 (2026-01-26)

Features
  • integrations: Add Chat & Notify integrations (cc692ed)
  • mocks: add streaming methods for various services (889b407)

v1.18.0

Compare Source

1.18.0

🚀 Features
  • feat(settings): Added support for inactive_resource_access_tokens_delete_after_days to the... (!2686) by Preethi Atchudan
🔄 Other Changes

1.18.0 (2026-01-25)

Features
  • settings: Added support for inactive_resource_access_tokens_delete_after_days to the... (52b60c3)

v1.17.0

Compare Source

1.17.0

🚀 Features

1.17.0 (2026-01-23)

v1.16.0

Compare Source

1.16.0

🚀 Features
  • Add environment, deployed_after, and deployed_before params to merge requests options struct (!2672) by Filip Aleksic
🔄 Other Changes

1.16.0 (2026-01-20)

v1.15.0

Compare Source

1.15.0

🚀 Features
  • Add ExpiresAt field to ProjectSharedWithGroup struct (!2671) by cindy
🔄 Other Changes

1.15.0 (2026-01-20)

Bug Fixes
  • Deprecate incorrect fields returned in response for Emails on Push integration (71d747d)
Features
  • convert examp

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.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • 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
Copy link
Author

red-hat-konflux bot commented Jan 13, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact 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: github.com/imdario/mergo@v1.0.2: parsing go.mod:
	module declares its path as: dario.cat/mergo
	        but was required as: github.com/imdario/mergo

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.3/major-go-deps branch 3 times, most recently from 61ec6b1 to 71c6f38 Compare January 21, 2026 01:31
@tommyd450 tommyd450 force-pushed the konflux/mintmaker/release-1.3/major-go-deps branch from 71c6f38 to 4fb1948 Compare January 23, 2026 14:45
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.3/major-go-deps branch 9 times, most recently from 9a59d1d to 04f7262 Compare January 28, 2026 21:17
@red-hat-konflux
chore(deps): update go dependencies to v1
1f89cfc 
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.3/major-go-deps branch from 04f7262 to 1f89cfc Compare January 29, 2026 01:19
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies to v1 (major) chore(deps): update go dependencies to v1 (major) - abandoned Feb 4, 2026
@red-hat-konflux
Copy link
Author

red-hat-konflux bot commented Feb 4, 2026

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies to v1 (major) - abandoned chore(deps): update go dependencies to v1 (major) Feb 4, 2026
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies to v1 (major) chore(deps): update go dependencies to v1 (major) - abandoned Feb 5, 2026
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update go dependencies to v1 (major) - abandoned chore(deps): update go dependencies to v1 (major) Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants