Update several nugets in PoC and Test Adapter

[josesimoes]

Description

• nanoFramework.TestFramework to v2.1.113
• nanoFramework.Runtime.Native to v1.7.1
• nanoFramework.Tools.Debugger.Net to v2.4.47

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 dependency versions for improved stability and performance.
    • nanoFramework.Tools.Debugger.Net updated to version 2.4.47.
    • Nerdbank.GitVersioning updated to version 3.6.146.

[coderabbitai]

Walkthrough

The changes in this pull request involve updates to the packages.lock.json file within the source/TestAdapter directory. Specifically, the versions of two dependencies have been modified: nanoFramework.Tools.Debugger.Net has been updated from version 2.4.42 to 2.4.47, and Nerdbank.GitVersioning has been updated from version 3.6.139 to 3.6.146. The content hashes for these dependencies have also changed, while all other dependencies remain unchanged.

Changes

File	Change Summary
source/TestAdapter/packages.lock.json	Updated nanoFramework.Tools.Debugger.Net from 2.4.42 to 2.4.47 and Nerdbank.GitVersioning from 3.6.139 to 3.6.146. Content hashes updated accordingly.

Possibly related PRs

• Update Microsoft.TestPlatform.ObjectModel for dependabot #257: This PR updates the Nerdbank.GitVersioning dependency, which is also updated in the main PR, indicating a direct relationship in terms of dependency management.
• Update 1 NuGet dependencies #264: This PR updates the Nerdbank.GitVersioning dependency from 3.6.139 to 3.6.141, which is relevant as the main PR also updates this dependency.
• Update 1 NuGet dependencies #267: This PR updates the Nerdbank.GitVersioning dependency from 3.6.141 to 3.6.143, showing a progression in version updates that relates to the main PR.
• Update 1 NuGet dependencies #275: This PR updates the Nerdbank.GitVersioning dependency from 3.6.143 to 3.6.146, which matches the version update in the main PR, establishing a clear connection.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between c0319c1 and f8800c0.

⛔ Files ignored due to path filters (5)

• poc/TestOfTestFramework/NFUnitTest.nfproj is excluded by none and included by none
• poc/TestOfTestFramework/packages.config is excluded by none and included by none
• poc/TestOfTestFrameworkByReference/NFUnitTestByReference.nfproj is excluded by none and included by none
• poc/TestOfTestFrameworkByReference/packages.config is excluded by none and included by none
• 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)

🔇 Additional comments (3)

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

40-42: LGTM: nanoFramework.Tools.Debugger.Net update.

The update from version 2.4.42 to 2.4.47 has been properly applied with the correct content hash.

---

51-53: LGTM: Nerdbank.GitVersioning update.

The update from version 3.6.139 to 3.6.146 has been properly applied with the correct content hash.

---

Line range hint 1-180: Verify missing package updates mentioned in PR objectives.

The PR objectives mention updates to:

• nanoFramework.TestFramework to 2.1.113
• nanoFramework.Runtime.Native to 1.7.1

However, these updates are not reflected in the packages.lock.json file. Please verify if these updates should be included in this PR.

---

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.