Version bump

[emmanuelrobles]

Description

Bump 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
  • Updated project to version 2.12.0.
  • Updated shared dependency versions.

[coderabbitai]

Walkthrough

Project version incremented from 2.11.0 to 2.12.0 in both <Version> and <FileVersion> tags. Shared dependency versions updated: CommonLibsStableVersion from 4.6.0 to 4.6.1, and CommonLibsReleaseVersion to a non-dev variant, affecting downstream package selections.

Changes

Cohort / File(s)	Summary
Version and Dependency Metadata Sharphound.csproj	Updated project version from 2.11.0 to 2.12.0 (<Version> and <FileVersion>). Advanced CommonLibsStableVersion from 4.6.0 to 4.6.1 and changed CommonLibsReleaseVersion from dev build to stable release variant (4.6.1), affecting shared library package selection logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A hop and a bump, version two-twelve takes the stage,
Dependencies dance to the rhythm of change,
Stable and steady, the libraries advance,
While metadata sparkles—a versioning waltz! ✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is largely incomplete. While it marks the correct change type (Chore) and includes the associated issue, the 'Motivation and Context' section and 'How Has This Been Tested?' section are entirely missing.	Add a 'Motivation and Context' section explaining why the version bump is necessary and complete the 'How Has This Been Tested?' section with testing details.
Title check	❓ Inconclusive	The title 'Version bump' is vague and generic, lacking specificity about what version was bumped or why.	Consider a more specific title like 'Bump SharpHound version to 2.12.0' to clearly indicate the version change and affected component.

✅ Passed checks (1 passed)

Check name	Status	Explanation
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 docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/BED-7885-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.}