Update dependencies

[josesimoes]

Description

• nanoFramework.Tools.Debugger.Net v2.5.10.
• Nerdbank.GitVersioning v3.7.115.

Motivation and Context

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

Summary by CodeRabbit

• Chores
  • Updated nanoFramework.Tools.Debugger.Net to version 2.5.10
  • Updated Nerdbank.GitVersioning to version 3.7.115

[coderabbitai]

Walkthrough

This pull request involves updating the packages.lock.json file in the source/TestAdapter directory. Specifically, two dependencies have been upgraded: nanoFramework.Tools.Debugger.Net from version 2.5.6 to 2.5.10, and Nerdbank.GitVersioning from version 3.7.112 to 3.7.115. The changes are limited to version updates and corresponding content hash modifications, maintaining the overall structure of the dependency lock file.

Changes

File	Change Summary
source/TestAdapter/packages.lock.json	- Updated nanoFramework.Tools.Debugger.Net from v2.5.6 to v2.5.10 - Updated Nerdbank.GitVersioning from v3.7.112 to v3.7.115

Possibly related PRs

• Update Microsoft.TestPlatform.ObjectModel for dependabot #257: Updates the Nerdbank.GitVersioning dependency, showing a similar focus on dependency version management
• Update 1 NuGet dependencies #260: Updates the Nerdbank.GitVersioning dependency from 3.6.133 to 3.6.139
• Update 1 NuGet dependencies #296: Involves updates to the Nerdbank.GitVersioning dependency

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 653286e and 11315fc.

⛔ Files ignored due to path filters (1)

• source/TestAdapter/nanoFramework.TestAdapter.csproj is excluded by none and included by none

📒 Files selected for processing (1)

• source/TestAdapter/packages.lock.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: nanoFramework.TestFramework (Build_Test_Framework)
• GitHub Check: nanoFramework.TestFramework (Get_Build_Flags)

🔇 Additional comments (3)

source/TestAdapter/packages.lock.json (3)

Line range hint 1-300: LGTM! Package lock file is consistent

The dependency updates are consistently applied across both target frameworks (.NET Framework 4.8 and .NET 6.0), and the lock file maintains its structural integrity.

---

49-51: LGTM! Patch version update for Nerdbank.GitVersioning

The update from 3.7.112 to 3.7.115 is a patch version bump, indicating backward-compatible bug fixes.

Let's verify if there are any breaking changes or significant updates in the changelog:

Also applies to: 193-195

✅ Verification successful

✅ Verified: Safe to update Nerdbank.GitVersioning to 3.7.115

The changes between 3.7.112 and 3.7.115 are backward-compatible bug fixes for tag-related operations and a helpful warning enhancement for version format mismatches.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changelog for Nerdbank.GitVersioning between versions 3.7.112 and 3.7.115

# Fetch release notes from GitHub
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/dotnet/Nerdbank.GitVersioning/releases \
  --jq 'map(select(.tag_name | startswith("v3.7.") and . >= "v3.7.112" and . <= "v3.7.115")) | .[].body'

Length of output: 3483

---

39-41: LGTM! Minor version update for nanoFramework.Tools.Debugger.Net

The update from 2.5.6 to 2.5.10 is a minor version bump that maintains the same dependencies, suggesting backward-compatible improvements.

Let's verify if there are any breaking changes or significant updates in the changelog:

Also applies to: 183-185

✅ Verification successful

✅ Safe to update: Changes are backward-compatible

Changes from 2.5.6 to 2.5.10 include:

• Bug fix for configuration block deployment
• Testability improvements
• Property change notification enhancements

No breaking changes identified in the release notes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changelog for nanoFramework.Tools.Debugger.Net between versions 2.5.6 and 2.5.10

# Fetch release notes from GitHub
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nf-debugger/releases \
  --jq 'map(select(.tag_name | startswith("v2.5.") and . >= "v2.5.6" and . <= "v2.5.10")) | .[].body'

Length of output: 190

---

Script:

#!/bin/bash
# First, search for the repository
echo "Searching for repository..."
gh search repos nanoframework/debugger --limit 5

echo -e "\nChecking for changelog files..."
# Clone and search for changelog files
git clone --depth 1 https://github.com/nanoframework/nf-debugger.git 2>/dev/null || true
if [ -d "nf-debugger" ]; then
    cd nf-debugger
    find . -type f -iname "*changelog*" -o -iname "*release*" -o -iname "*history*"
    cd ..
fi

# Try alternative repository name
echo -e "\nTrying alternative repository..."
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nf-debugger/releases \
  --jq 'map(select(.name | contains("v2.5."))) | .[0:3] | .[].name'

Length of output: 932

---

Script:

#!/bin/bash
# Read the changelog content for relevant versions
cd nf-debugger
echo "Changelog entries between v2.5.6 and v2.5.10:"
awk '/## \[v2\.5\.10\]/, /## \[v2\.5\.6\]/' CHANGELOG.md

echo -e "\nChecking for breaking changes keywords:"
awk '/## \[v2\.5\.10\]/, /## \[v2\.5\.6\]/' CHANGELOG.md | grep -i -E 'break|deprecat|remov|chang|updat' || true

Length of output: 385

---

Script:

#!/bin/bash
echo "Searching changelog with different patterns:"
cd nf-debugger
echo "=== Method 1: Direct grep ==="
grep -A 5 -B 1 "2\.5\.\(10\|8\|6\)" CHANGELOG.md || true

echo -e "\n=== Method 2: GitHub release notes ==="
cd ..
for version in "2.5.10" "2.5.8" "2.5.6"; do
    echo "=== Version $version ==="
    gh api \
        -H "Accept: application/vnd.github+json" \
        repos/nanoframework/nf-debugger/releases/tags/v$version \
        --jq '.body' || true
done

Length of output: 1691

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.