bump version to 4.6.1

[emmanuelrobles]

Description

bump nuget version

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 bumped to 4.6.1

[coderabbitai]

Walkthrough

The package version in Directory.Build.props was incremented from 4.6.0 to 4.6.1. This single-line change updates the build metadata version used for project packaging and distribution.

Changes

Cohort / File(s)	Summary
Version Bump Directory.Build.props	Package version incremented from 4.6.0 to 4.6.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

Suggested reviewers

• mykeelium

Poem

🐰 A tiny bump, from point-oh to point-one,
The version grows, our work is done!
Four-six-one now takes the stage,
A fresh release turns another page. 📦✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'bump version to 4.6.1' directly and accurately describes the main change: incrementing the package version from 4.6.0 to 4.6.1 in Directory.Build.props.
Description check	✅ Passed	The description is largely complete with key sections filled out: Description provided, change type marked correctly as Chore, and most checklist items completed. Missing sections include Motivation and Context, How Has This Been Tested, and Screenshots, which are non-critical for a simple version bump chore.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/BED-7885-SHC-bump-version

---

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 the current code and only fix it if needed.

Inline comments:
In `@Directory.Build.props`:
- Line 10: Add a new CHANGELOG.md entry for the release matching the updated
<Version>4.6.1</Version> in Directory.Build.props: create a "## [4.6.1] -
YYYY-MM-DD" section (use the correct release date) and list the included bug
fixes, changes, and any upgrade notes or breaking changes; ensure the entry
follows the existing changelog format (e.g., sections like "Fixed", "Changed",
"Added") and references any key fixes or PR numbers that correspond to this
patch.

🪄 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: 490184ce-4d3a-4cf5-a749-6ffaaba21f53

📥 Commits

Reviewing files that changed from the base of the PR and between 73ecc6c and fd39cbf.

📒 Files selected for processing (1)

• Directory.Build.props