chore: bump SHC for rc - BED-8300

[mykeelium]

Description

Bumps the version of the SharpHoundCommon library for a rc release.

Motivation and Context

This PR addresses: BED-8300

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
  • Updated project version to 4.6.2-rc1 (release candidate)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a525092e-3b0b-430c-baa5-71f043666157

📥 Commits

Reviewing files that changed from the base of the PR and between d304898 and 485c33a.

📒 Files selected for processing (1)

• Directory.Build.props

---

Walkthrough

The centralized MSBuild version property is updated from 4.6.1 to 4.6.2-rc1 in Directory.Build.props, advancing the project to a prerelease version that will apply across all build outputs.

Changes

Prerelease Version Bump

Layer / File(s)	Summary
Version property update Directory.Build.props	The shared Version MSBuild property is bumped from 4.6.1 to the prerelease 4.6.2-rc1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• SpecterOps/SharpHoundCommon#271: Both PRs update project version values to prepare for release.

Suggested reviewers

• definitelynotagoblin
• ktstrader

Poem

🐰 A tiny hop, a version bump,
From stable ground to prerelease lump,
Four point six to two so bright,
The rabbit blesses this build tonight! 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically identifies the main change: bumping the version of SharpHoundCommon for a release candidate, and references the associated ticket.
Description check	✅ Passed	The description covers the main sections of the template including purpose, motivation/context, type of change (chore), and completed checklist items. However, the testing section is empty.
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-8300

---

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