-
Notifications
You must be signed in to change notification settings - Fork 76
fix(deps): update misc go deps OLD #596
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.
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
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
11f9901
to
c4306b7
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
c4306b7
to
f753df2
Compare
@github-actions[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Signed-off-by: cert-manager-bot <[email protected]>
f753df2
to
5698533
Compare
This PR contains the following updates:
v1.18.1
->v1.18.2
v1.38.0
->v1.38.2
v1.9.1
->v1.10.1
v1.0.7
->v1.0.9
v1.10.0
->v1.11.1
v1.74.2
->v1.75.0
v1.36.7
->v1.36.8
Release Notes
cert-manager/cert-manager (github.com/cert-manager/cert-manager)
v1.18.2
Compare Source
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
We fixed a bug in the CSR's name constraints construction (only applies if you have enabled the
NameConstraints
feature gate).We dropped the new
global.rbac.disableHTTPChallengesRole
Helm option due to a bug we found, this feature will be released inv1.19
instead.Changes since
v1.18.1
:Bug or Regression
global.rbac.disableHTTPChallengesRole
Helm option. (#7837, @cert-manager-bot)onsi/gomega (github.com/onsi/gomega)
v1.38.2
Compare Source
1.38.2
c404969
]v1.38.1
Compare Source
1.38.1
Fixes
Numerous minor fixes and dependency bumps
spf13/cobra (github.com/spf13/cobra)
v1.10.1
Compare Source
🐛 Fix
v1.0.9 of pflags brought back
ParseErrorsWhitelist
and marked it as deprecatedFull Changelog: spf13/cobra@v1.10.0...v1.10.1
v1.10.0
Compare Source
What's Changed
🚨 Attention!
This version of
pflag
carried a breaking change: it renamedParseErrorsWhitelist
toParseErrorsAllowlist
which can break builds if bothpflag
andcobra
are dependencies in your project.pflag and
cobra, upgrade
pflagto 1.0.8 and
cobrato
1.10.0`pflag
v1.0.9 which keeps the deprecatedParseErrorsWhitelist
More details can be found here: #2303 (comment)
✨ Features
🐛 Fix
🪠 Testing
📝 Docs
New Contributors
Full Changelog: spf13/cobra@v1.9.1...v1.9.2
spf13/pflag (github.com/spf13/pflag)
v1.0.9
Compare Source
What's Changed
Full Changelog: spf13/pflag@v1.0.8...v1.0.9
v1.0.8
Compare Source
This version, while only a patch bump, includes a (very minor) breaking change: the
flag.ParseErrorsWhitelist
struct and correspondingFlagSet.parseErrorsWhitelist
field have been renamed toParseErrorsAllowlist
.This should result in compilation errors in any code that uses these fields, which can be fixed by adjusting the names at call sites. There is no change in semantics or behavior of the struct or field referred to by these names. If your code compiles without errors after bumping to/past v1.0.8, you are not affected by this change.
The breaking change was reverted in v1.0.9, by means of re-introducing the old names with deprecation warnings. The plan is still to remove them in a future release, so if your code does depend on the old names, please change them to use the new names at your earliest convenience.
What's Changed
New Contributors
Full Changelog: spf13/pflag@v1.0.7...v1.0.8
stretchr/testify (github.com/stretchr/testify)
v1.11.1
Compare Source
This release fixes #1785 introduced in v1.11.0 where expected argument values implementing the stringer interface (
String() string
) with a method which mutates their value, when passed to mock.Mock.On (m.On("Method", <expected>).Return()
) or actual argument values passed to mock.Mock.Called may no longer match one another where they previously did match. The behaviour prior to v1.11.0 where the stringer is always called is restored. Future testify releases may not call the stringer method at all in this case.What's Changed
Full Changelog: stretchr/testify@v1.11.0...v1.11.1
v1.11.0
Compare Source
What's Changed
Functional Changes
v1.11.0 Includes a number of performance improvements.
Fixes
Documentation, Build & CI
New Contributors
Full Changelog: stretchr/testify@v1.10.0...v1.11.0
grpc/grpc-go (google.golang.org/grpc)
v1.75.0
: Release 1.75.0Compare Source
Behavior Changes
DelayedPickComplete
event, a type alias ofPickerUpdated
. (#8465)PickerUpdated
symbol.grpc.WithAuthority
as the highest-priority option for setting authority, above the setting in the credentials themselves. (#8488)WithAuthority
is available, the credentials should not be used to override the authority.New Features
GRPC_ENABLE_TXT_SERVICE_CONFIG
) to provide a way to disable TXT lookups in the DNS resolver (by setting it tofalse
). By default, TXT lookups are enabled, as they were previously. (#8377)Bug Fixes
call
andendpoint
in curly braces to comply with UCUM and gRPC OpenTelemetry guidelines. (#8481)grpc.NewClient(":<port-number-or-name>")
). (#8488)protocolbuffers/protobuf-go (google.golang.org/protobuf)
v1.36.8
Compare Source
Maintenance:
CL/696316: all: set Go language version to Go 1.23
CL/696315: types: regenerate using latest protobuf v32 release
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.
This PR has been generated by Renovate Bot.