-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Update github.com/Azure/azure-event-hubs-go/v3 #2986
Labels
feature-request
All issues for new features that have not been committed to
needs-discussion
stale-bot-ignore
All issues that should not be automatically closed by our stale bot
Comments
JorTurFer
added
needs-discussion
feature-request
All issues for new features that have not been committed to
labels
May 3, 2022
JorTurFer
changed the title
Update bump github.com/Azure/azure-event-hubs-go/v3
Update github.com/Azure/azure-event-hubs-go/v3
May 3, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
JorTurFer
added
the
stale-bot-ignore
All issues that should not be automatically closed by our stale bot
label
Jul 2, 2022
I think that go 1.18 is required because to bump these deps we need to use the new package for service bus |
1 task
Repository owner
moved this from To Do
to Ready To Ship
in Roadmap - KEDA Core
Sep 15, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
feature-request
All issues for new features that have not been committed to
needs-discussion
stale-bot-ignore
All issues that should not be automatically closed by our stale bot
Proposal
Dependabot has created a PR suggesting the update from
3.3.16
to3.3.18
but it's not mergeable because the build fails.There is a problem with our dependencies' tree that needs to be fixed manually (updating also some code)
Also together with
github.com/Azure/azure-amqp-common-go/v3
dependency.Use-Case
Improve the security applying latest versions of the dependencies
Anything else?
No response
The text was updated successfully, but these errors were encountered: