-
Notifications
You must be signed in to change notification settings - Fork 3.4k
chore(deps): bump github.com/argoproj/argo-events from 1.9.1 to 1.9.6 in the go_modules group #14382
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
chore(deps): bump github.com/argoproj/argo-events from 1.9.1 to 1.9.6 in the go_modules group #14382
Conversation
|
@Joibel While building binary with argo-events v1.9.6 I am seeing the following failures. github.com/argoproj/argo-events/pkg/client/eventsource/clientset/versioned --> github.com/argoproj/argo-events/pkg/client/clientset/versioned github.com/argoproj/argo-events/pkg/client/sensor/clientset/versioned. --> github.com/argoproj/argo-events/pkg/client/clientset/versioned |
Even I am facing the same issue |
a1fe54c to
57b101f
Compare
Bumps the go_modules group with 1 update: [github.com/argoproj/argo-events](https://github.com/argoproj/argo-events). Updates `github.com/argoproj/argo-events` from 1.9.1 to 1.9.6 - [Release notes](https://github.com/argoproj/argo-events/releases) - [Changelog](https://github.com/argoproj/argo-events/blob/master/CHANGELOG.md) - [Commits](argoproj/argo-events@v1.9.1...v1.9.6) Manually refactored the code necessary for this where the events clients need updating - moving to a single client instead of separate event source and sensor clients As this bumps prometheus-go switch to the legacy name verifier for metrics as the new name verifier doesn't match our documented rules. This could be fixed elsewhere separately from this. --- updated-dependencies: - dependency-name: github.com/argoproj/argo-events dependency-version: 1.9.6 dependency-type: direct:production dependency-group: go_modules ... Signed-off-by: dependabot[bot] <support@github.com>
57b101f to
b53eb3a
Compare
Bumps the go_modules group with 1 update: github.com/argoproj/argo-events.
Updates
github.com/argoproj/argo-eventsfrom 1.9.1 to 1.9.6-- Manual changes by Alan Clucas
Manually refactored the code necessary for this where the events
clients need updating - moving to a single client instead of separate
event source and sensor clients
As this bumps prometheus-go switch to the legacy name verifier for
metrics as the new name verifier doesn't match our documented
rules. This could be fixed elsewhere separately from this.
Release notes
Sourced from github.com/argoproj/argo-events's releases.
... (truncated)
Changelog
Sourced from github.com/argoproj/argo-events's changelog.
... (truncated)
Commits
80f5951Update manifests to v1.9.6c66510cchore(deps): bump google.golang.org/api from 0.227.0 to 0.228.0 (#3539)2167912chore(deps): bump github.com/pkg/sftp from 1.13.8 to 1.13.9 (#3541)534f86achore(deps): bump github.com/minio/minio-go/v7 from 7.0.88 to 7.0.89 (#3536)4810317chore(deps): bump github.com/nats-io/nats.go from 1.39.1 to 1.41.0 (#3547)7aa57ffchore(deps): bump sigs.k8s.io/controller-tools from 0.16.3 to 0.17.3 (#3545)b65ab16chore(deps): bump google.golang.org/grpc from 1.71.0 to 1.71.1 (#3546)02c9a5echore(deps): bump gitlab.com/gitlab-org/api/client-go from 0.126.0 to 0.127.0...616288fdocs: Update PDB apiVersion (#3535)db1ba6echore(deps): bump github.com/golang-jwt/jwt/v5 from 5.2.1 to 5.2.2 (#3529)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.