SharpHoundCommon and SharpHoundRPC Version Mismatch in Sharphound.csproj

[shogunlab]

Hey there. I noticed that in previous SharpHoundCommon version bump commits such as 0dff518 and a18a982, both SharpHoundCommon and SharpHoundRPC package references receive a version bump in the Sharphound.csproj file. But, in the commit 64ef0e5, only SharpHoundCommon is updated to 4.0.9 while SharpHoundRPC remains on 4.0.8.

Was this intentional? If not, would it make sense to bump the SharpHoundRPC version in the package reference as well? If it was intentional, please feel free to close this issue and disregard. Thank you!

[rvazarkar]

Its not intentional, but it's also not going to affect anything. The RPC library hasn't received any updates in a significant period of time. At some point, I'll look into making the RPC library a pinned version along with the CommonLib. I'll make sure to update it in an upcoming MR, or if you'd like to make an MR for it, feel free and I'll accept it :)

[shogunlab]

Sounds good! Thank you for clarifying. Then yeah, I'll submit a pull request with an update to have the SharpHoundRPC version bumped to 4.0.9 in the 2.X branch.