Thank you for your interest in contributing to wormhole-william.
I should apologize that we have never written down exactly what our dependency policy is. Let me correct that oversight now.
Our policy for upgrading dependencies is that we do not churn dependency versions simply because there is a new version available. Upgrading dependencies requires extensive code reviews and testing that is a fairly large burden to do every time there's a new version. Instead we upgrade dependencies for the following reasons:
A security vulnerability that impacts us (i.e. govulncheck says we are impacted or we can reason out that we are impacted)
A bug that impacts us
A significant performance improvement that is measurable
A new feature/api that is required for feature development in wormhole-william
If you believe that this PR falls into one of the above categories then we can have a discussion about that for each dependency change. Otherwise you can close out this issue.
Thank you again for your interest in contributing to wormhole-william.
Thank you for your interest in contributing to wormhole-william.
I should apologize that we have never written down exactly what our dependency policy is. Let me correct that oversight now.
Our policy for upgrading dependencies is that we do not churn dependency versions simply because there is a new version available. Upgrading dependencies requires extensive code reviews and testing that is a fairly large burden to do every time there's a new version. Instead we upgrade dependencies for the following reasons:
If you believe that this PR falls into one of the above categories then we can have a discussion about that for each dependency change. Otherwise you can close out this issue.
Thank you again for your interest in contributing to wormhole-william.