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 version of the Nerdbank.GitVersioning dependency to enhance compatibility and performance.

[coderabbitai]

Walkthrough

The changes in this pull request involve an update to the packages.lock.json file for the nanoFramework.Device.OneWire project. Specifically, the version of the Nerdbank.GitVersioning dependency has been updated from 3.6.143 to 3.6.146, along with an updated content hash. The dependency on nanoFramework.CoreLibrary remains unchanged.

Changes

File	Change Summary
nanoFramework.Device.OneWire/packages.lock.json	Updated Nerdbank.GitVersioning version from 3.6.143 to 3.6.146

Possibly related PRs

• Update 1 NuGet dependencies #99: This PR updates the Nerdbank.GitVersioning dependency from 3.6.133 to 3.6.139, which is a direct precursor to the version change in the main PR.
• Update 1 NuGet dependencies #101: This PR updates the Nerdbank.GitVersioning dependency from 3.6.139 to 3.6.141, continuing the version progression leading up to the main PR's change.
• Update 1 NuGet dependencies #103: This PR updates the Nerdbank.GitVersioning dependency from 3.6.141 to 3.6.143, which is the version immediately preceding the update in the main PR.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 46bcd0e and b663e6b.

⛔ Files ignored due to path filters (2)

• nanoFramework.Device.OneWire/nanoFramework.Device.OneWire.nfproj is excluded by none and included by none
• nanoFramework.Device.OneWire/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.Device.OneWire/packages.lock.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

nanoFramework.Device.OneWire/packages.lock.json (1)

13-15: LGTM! Version update looks correct.

The update of Nerdbank.GitVersioning from 3.6.143 to 3.6.146 is properly reflected in the lock file with corresponding content hash update.

Let's verify that this version matches the package manifest:

✅ Verification successful

Let's try a different approach to find the package references by first locating the relevant files and then checking their content.

---

Let's try one final approach using a more specific search in the directory where the packages.lock.json was found:

---

I notice that we have a packages.config file in the directory. Let's check its content as it should contain the package reference information:

---

Version update is correctly reflected across all package references

The version update to Nerdbank.GitVersioning 3.6.146 is consistently reflected in:

• packages.lock.json
• packages.config
• nfproj file (in both import statements and target references)

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the version in packages.lock.json matches Directory.Packages.props or .csproj files
# Expect: The same version (3.6.146) in the package reference

# Search for Nerdbank.GitVersioning package reference in props files
echo "Checking Directory.Packages.props..."
rg -l "PackageVersion.*Nerdbank.GitVersioning" --glob "Directory.*.props"

# Search for Nerdbank.GitVersioning package reference in project files
echo "Checking .csproj files..."
rg -l "PackageReference.*Nerdbank.GitVersioning" --glob "*.csproj"

Length of output: 586

---

Script:

#!/bin/bash
# First, find all props and csproj files
echo "Finding all props and csproj files..."
fd -e props -e csproj

# Then check their content for Nerdbank.GitVersioning references
echo -e "\nChecking content for Nerdbank.GitVersioning..."
fd -e props -e csproj -x cat {} \; | grep -A 2 -B 2 "Nerdbank.GitVersioning"

Length of output: 297

---

Script:

#!/bin/bash
# Find the package references in the specific project directory
echo "Checking nanoFramework.Device.OneWire directory..."
ls -la nanoFramework.Device.OneWire/

echo -e "\nChecking package references in project files..."
if [ -f "nanoFramework.Device.OneWire/nanoFramework.Device.OneWire.csproj" ]; then
    cat "nanoFramework.Device.OneWire/nanoFramework.Device.OneWire.csproj"
fi

echo -e "\nChecking for Directory.Build.props..."
if [ -f "Directory.Build.props" ]; then
    cat "Directory.Build.props"
fi

Length of output: 975

---

Script:

#!/bin/bash
echo "Checking packages.config content..."
cat "nanoFramework.Device.OneWire/packages.config"

echo -e "\nChecking nfproj file content..."
cat "nanoFramework.Device.OneWire/nanoFramework.Device.OneWire.nfproj"

Length of output: 5018

---

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.