Skip to content

chore: bump version v4.3.0 #228

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Jul 22, 2025
Merged

chore: bump version v4.3.0 #228

merged 1 commit into from
Jul 22, 2025

Conversation

definitelynotagoblin
Copy link
Contributor

@definitelynotagoblin definitelynotagoblin commented Jul 22, 2025 •
edited by coderabbitai bot
Loading

Description

Cutting version 4.3.0

Motivation and Context

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
    • Updated package version numbers for SharpHoundCommonLib and SharpHoundRPC to 4.3.0.

@definitelynotagoblin definitelynotagoblin self-assigned this Jul 22, 2025
@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Jul 22, 2025 •
edited
Loading

Walkthrough

The version numbers in the project files for SharpHoundCommonLib and SharpHoundRPC were incremented to 4.3.0. No other modifications were made to configurations, dependencies, or public interfaces.

Changes

Files Change Summary
src/CommonLib/SharpHoundCommonLib.csproj Updated package version from 4.2.8 to 4.3.0
src/SharpHoundRPC/SharpHoundRPC.csproj Updated package version from 4.2.1 to 4.3.0

Estimated code review effort

1 (~2 minutes)

Poem

A hop and a skip, version numbers climb,
From 4.2 to 4.3, right on time!
No code to review, just numbers anew,
The bunnies rejoice—our work here is through.
🐇✨

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

coderabbitai[bot]
coderabbitai bot reviewed Jul 22, 2025
View reviewed changes
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/SharpHoundRPC/SharpHoundRPC.csproj (1)

11-11: Optional: populate <PackageReleaseNotes> for NuGet consumers.
Adding release-note metadata makes it easier for users to see what changed without consulting the repo.

src/CommonLib/SharpHoundCommonLib.csproj (1)

12-12: Optional: include release notes & ensure downstream range constraints are updated.
If other projects pin a strict version, make sure they allow 4.3.0, and consider adding <PackageReleaseNotes> here as well.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 88d8303 and 0a76aef.

📒 Files selected for processing (2)
  • src/CommonLib/SharpHoundCommonLib.csproj (1 hunks)
  • src/SharpHoundRPC/SharpHoundRPC.csproj (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (2)
src/SharpHoundRPC/SharpHoundRPC.csproj (1)

11-11: Version bump to 4.3.0 looks correct and consistent with the release plan.
No additional issues spotted.

src/CommonLib/SharpHoundCommonLib.csproj (1)

12-12: Version bump to 4.3.0 looks good.
The change keeps CommonLib in sync with SharpHoundRPC.

@definitelynotagoblin definitelynotagoblin enabled auto-merge (squash) July 22, 2025 20:32
@definitelynotagoblin definitelynotagoblin merged commit bea975e into v4 Jul 22, 2025
2 checks passed
@definitelynotagoblin definitelynotagoblin deleted the v4.3.0-bump branch July 22, 2025 20:36
@github-actions github-actions bot locked and limited conversation to collaborators Jul 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

@ktstrader ktstrader ktstrader approved these changes

Assignees

@definitelynotagoblin definitelynotagoblin

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@definitelynotagoblin @ktstrader