Update 1 NuGet dependencies

[nfbot]

Bumps Nerdbank.GitVersioning from 3.6.143 to 3.6.146

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the Nerdbank.GitVersioning dependency to enhance stability and performance.

[coderabbitai]

Walkthrough

The changes involve an update to the Nerdbank.GitVersioning dependency in the System.Device.Wifi/packages.lock.json file. The version has been incremented from 3.6.143 to 3.6.146, accompanied by an update to the contentHash. All other dependencies in the file remain unchanged.

Changes

File	Change Summary
System.Device.Wifi/packages.lock.json	Updated Nerdbank.GitVersioning version from 3.6.143 to 3.6.146, updated contentHash. Other dependencies unchanged.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 077f1bf and f0ac179.

⛔ Files ignored due to path filters (2)

• System.Device.Wifi/System.Device.Wifi.nfproj is excluded by none and included by none
• System.Device.Wifi/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• System.Device.Wifi/packages.lock.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

System.Device.Wifi/packages.lock.json (1)

43-45: LGTM: Nerdbank.GitVersioning dependency updated successfully.

The update of Nerdbank.GitVersioning from version 3.6.143 to 3.6.146 has been correctly implemented in the packages.lock.json file. This change aligns with the PR objectives and is consistent with the automated nature of the update.

As this is an automated update, it's recommended to verify that the project builds successfully and passes all tests with the new dependency version. Run the following script to check for any potential build issues:

✅ Verification successful

Verified: Nerdbank.GitVersioning dependency update confirmed.

The Nerdbank.GitVersioning package has been successfully updated from version 3.6.143 to 3.6.146 across all relevant files. All references to the old version have been removed, ensuring a clean update.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for potential build issues after dependency update

# Test: Search for build or test files that might need to be updated
echo "Searching for build and test files:"
fd -e yaml -e yml -e json -e xml -e csproj -e sln

# Test: Check if Nerdbank.GitVersioning is referenced in other files
echo "Checking for other references to Nerdbank.GitVersioning:"
rg "Nerdbank.GitVersioning"

# Note: As we can't actually build or test the project in this environment,
# these checks are to help identify potential areas that might need attention.

Length of output: 1929

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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