SpecterOps / SpecterOps/SharpHound
SharpHoundCommon and SharpHoundRPC Version Mismatch in Sharphound.csproj
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 266
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
Hey there. I noticed that in previous SharpHoundCommon version bump commits such as https://github.com/BloodHoundAD/SharpHound/commit/0dff51835a1879e3b31f8494acd76dd72ac92fe6 and https://github.com/BloodHoundAD/SharpHound/commit/a18a9829c4c9e382a027cb8f1abf994e860199c5, both SharpHoundCommon and SharpHoundRPC package references receive a version bump in the Sharphound.csproj file. But, in the commit https://github.com/BloodHoundAD/SharpHound/commit/64ef0e56661734566b8bd0fc58d59c44c645c7fa, 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!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect Sharphound.csproj and compare the SharpHoundCommon and SharpHoundRPC package references with the version-bump commits linked in the issue. Confirm whether the 4.0.8 SharpHoundRPC reference is intentional; done means resolving the mismatch decision and updating the package reference if it is not intentional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, security, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100