chore: bump SHC to full version - BED-8367

[mykeelium]

Description

Bumps SharpHoundCommon to a full release version.

Motivation and Context

This PR addresses: BED-8367

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:

• I have met the contributing prerequisites
  • Assigned myself to this PR
  • Added the appropriate labels
  • Associated an issue: Issues and Pull Requests README BloodHound#672
  • Read the Contributing guide: https://github.com/SpecterOps/BloodHound/wiki/Contributing
• I have ensured that related documentation is up-to-date
  • Open API docs
  • Code comments
• I have followed proper test practices
  • Added/updated tests to cover my changes
  • All new and existing tests passed

Summary by CodeRabbit

• Chores
  • Version 4.6.2 is now available as a stable release.

[coderabbitai]

Walkthrough

The Directory.Build.props file updates the project version from 4.6.2-rc1 (release candidate) to 4.6.2 (final release), bumping the MSBuild Version property by one line.

Changes

Release version finalization

Layer / File(s)	Summary
Version property update Directory.Build.props	MSBuild Version property updated from 4.6.2-rc1 to 4.6.2.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Possibly related PRs

• SpecterOps/SharpHoundCommon#305: Both PRs modify the Directory.Build.props Version property between release candidate and final version strings.

Suggested reviewers

• definitelynotagoblin
• ktstrader

Poem

🐰 A version hops forward, from test to release,
RC fades to final—the build finds its peace,
Four-six-two, no longer a draft,
One tiny line tweak, and the project's uncracked! 🎉

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: bumping SharpHoundCommon (SHC) to a full release version from 4.6.2-rc1 to 4.6.2, with the related ticket reference.
Description check	✅ Passed	The description covers the main sections but the 'How Has This Been Tested?' section is empty, and the contributor checklist items are not marked as completed despite the change being ready for merge.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch BED-8367

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@Directory.Build.props`:
- Line 10: The project version in Directory.Build.props is set to 4.6.2 but
release artifacts are missing: create and push a git tag named v4.6.2 pointing
at the release commit and add a corresponding top-level entry for 4.6.2 in
CHANGELOG.md (copy/merge any notes from 4.6.2-rc1 if needed), ensuring there are
no remaining 4.6.2-rc1 references anywhere; reference the Version element in
Directory.Build.props and verify the git tag v4.6.2 and the CHANGELOG.md 4.6.2
entry are present before merging.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 98a3ac18-71cd-4bd6-8524-898ba16ce9c3

📥 Commits

Reviewing files that changed from the base of the PR and between 8a4583f and 90c615d.

📒 Files selected for processing (1)

• Directory.Build.props