-
Notifications
You must be signed in to change notification settings - Fork 261
Update old dependencies #2282
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 old dependencies #2282
Conversation
golang.org/x/sync v0.11.0 | ||
golang.org/x/sys v0.30.0 | ||
gotest.tools v2.2.0+incompatible | ||
gotest.tools/v3 v3.5.2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This clearly invites a question whether the project should be depending on both github.com/stretchr/testify
and gotest.tools/v3
.
Solving that is not a goal of this PR (which focuses on old/unmaintained/non-updated dependencies).
needs a rebase |
Rebased. |
@giuseppe PTANL. |
Should not change behavior. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
We have been using a version over 6 years old. Signed-off-by: Miloslav Trmač <mitr@redhat.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
…8cf8 Signed-off-by: Miloslav Trmač <mitr@redhat.com>
Signed-off-by: Miloslav Trmač <mitr@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: giuseppe, mtrmac The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Bots generally update direct dependencies, and dependencies with known vulnerabilities.
For indirect dependencies which are over a year old, and either have a newer tagged release or haven’t been using a tagged release anyway, update to the latest version.
(This does nothing about dependencies with no upstream activity, or officially deprecated or even archived.)