chore: version bump v2.9.0

[definitelynotagoblin]

Description

Version bump, SHCE v2.9.0

Motivation and Context

https://specterops.atlassian.net/browse/BED-7121

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Chore (a change that does not modify the application functionality)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• Documentation updates are needed, and have been made accordingly.
• I have added and/or updated tests to cover my changes.
• All new and existing tests passed.
• My changes include a database migration.

Summary by CodeRabbit

• Chores
  • Version bumped to 2.9.0
  • Package dependencies updated to latest compatible versions

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The Sharphound.csproj file was updated to bump the assembly and file versions from 2.8.1 to 2.9.0, and two package dependencies were updated: SharpHoundCommon and SharpHoundRPC both from 4.5.1 to 4.5.2.

Changes

Cohort / File(s)	Change Summary
Version and Dependency Updates Sharphound.csproj	Bumped AssemblyVersion and FileVersion from 2.8.1 to 2.9.0; updated SharpHoundCommon package from 4.5.1 to 4.5.2; updated SharpHoundRPC package from 4.5.1 to 4.5.2

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• BED-6848 chore: version bump to v2.8.1 #189: Also bumps assembly/file versions and updates SharpHoundCommon/SharpHoundRPC package references in the same project file.
• SHCE version bump to 2.8.0 #183: Performs version bumps in Sharphound.csproj for AssemblyVersion and FileVersion entries.
• [BED-6302] chore: Version bump to v #167: Updates both assembly/file versions and SharpHoundCommon/SharpHoundRPC package versions in Sharphound.csproj.

Suggested reviewers

• ktstrader
• MikeX777

Poem

🐰 Version bumps, oh what a delight,
Dependencies updated, shining bright!
From four-five-one to four-five-two,
Sharp Hound tools now feel fresh and new! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change as a version bump to v2.9.0, which matches the Sharphound.csproj file modifications shown in the changeset.
Description check	✅ Passed	The description includes most required sections: Description, Motivation and Context with a linked JIRA ticket, and Types of changes correctly marked as Chore. However, the 'How Has This Been Tested?' section is incomplete (only template comments, no actual testing details provided).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 70c2310 and 49104a4.

📒 Files selected for processing (1)

• Sharphound.csproj

🔇 Additional comments (2)

Sharphound.csproj (2)

9-10: LGTM!

Version and FileVersion are consistent and correctly bumped to 2.9.0.

---

28-29: LGTM!

Patch version bumps for SharpHoundCommon and SharpHoundRPC from 4.5.1 to 4.5.2 are straightforward dependency updates. As expected for internal SpecterOps packages, these versions are not available on the public NuGet feed and are likely hosted on a private package feed. Verify availability on your internal NuGet feed before merging.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}