Regular Dependency Update Cycle for Milvus #38053
nish112022
started this conversation in
Ideas & Feature requests
Replies: 2 comments
-
@nish112022 @LoveEachDay maybe it's reasonable to add a check |
Beta Was this translation helpful? Give feedback.
0 replies
-
Alright, I will do this.Time to time |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
EOL
End-of-life (EOL) refers to the point in time when an open-source software (OSS) project or a particular version of it will no longer be maintained or supported by the developers or the community. EOL software or outdated libraries no longer receive updates or patches, leaving them vulnerable to threats. Staying updated helps ensure security, compatibility, and performance improvements.
Now, milvus uses a lot of dependencies which we can see under go.mod ,go.sum and a lot of them are quite old [more than 6 months] and can be brought to the later versions.
But, this will keep on happening.So,I believe we should have some monthly/biweekly upgrade going on so that we try to be on the latest versions almost all the time.
One example of this is:
We currently use github.com/casbin/casbin/v2 at version v2.44.2. The latest in this series is v2.101.0, released on Nov 16, 2024, which includes numerous improvements and bug fixes.
Beta Was this translation helpful? Give feedback.
All reactions