Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.TestFramework from 3.0.47 to 3.0.49

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated nanoFramework.TestFramework dependency from version 3.0.47 to 3.0.49 across multiple test project configurations.

[coderabbitai]

Walkthrough

This pull request involves updating the nanoFramework.TestFramework dependency version from 3.0.47 to 3.0.49 across multiple test project packages.lock.json files. The update is consistent across three different test project directories: IPAddressTests, NetworkHelperTests, and SocketTests. The change appears to be a routine dependency version bump with updated content hashes reflecting the new version.

Changes

File	Change Summary
Tests/IPAddressTests/packages.lock.json	Updated nanoFramework.TestFramework from version 3.0.47 to 3.0.49
Tests/NetworkHelperTests/packages.lock.json	Updated nanoFramework.TestFramework from version 3.0.47 to 3.0.49
Tests/SocketTests/packages.lock.json	Updated nanoFramework.TestFramework from version 3.0.47 to 3.0.49

Possibly related PRs

• Update 1 NuGet dependencies #316: Updates nanoFramework.TestFramework from 2.1.94 to 2.1.100
• Update 1 NuGet dependencies #317: Updates nanoFramework.TestFramework from 2.1.100 to 2.1.104
• Update 1 NuGet dependencies #320: Updates nanoFramework.TestFramework from 2.1.104 to 2.1.107

---

📜 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 ed30956 and 1fb2a46.

⛔ Files ignored due to path filters (6)

• Tests/IPAddressTests/IPAddressTests.nfproj is excluded by none and included by none
• Tests/IPAddressTests/packages.config is excluded by none and included by none
• Tests/NetworkHelperTests/NetworkHelperTests.nfproj is excluded by none and included by none
• Tests/NetworkHelperTests/packages.config is excluded by none and included by none
• Tests/SocketTests/SocketTests.nfproj is excluded by none and included by none
• Tests/SocketTests/packages.config is excluded by none and included by none

📒 Files selected for processing (3)

• Tests/IPAddressTests/packages.lock.json (1 hunks)
• Tests/NetworkHelperTests/packages.lock.json (1 hunks)
• Tests/SocketTests/packages.lock.json (1 hunks)

🔇 Additional comments (3)

Tests/IPAddressTests/packages.lock.json (1)

25-27: LGTM: Version update is consistent with PR objectives

The update of nanoFramework.TestFramework to version 3.0.49 is properly reflected in both the requested and resolved versions, with the corresponding content hash update.

Tests/SocketTests/packages.lock.json (1)

25-27: LGTM: Version update matches across test projects

The nanoFramework.TestFramework update to 3.0.49 is consistent with other test projects, maintaining the same content hash.

Tests/NetworkHelperTests/packages.lock.json (1)

31-33: LGTM: Version update is consistent across all test projects

The nanoFramework.TestFramework update to 3.0.49 is properly applied, maintaining consistency with other test projects.

Let's verify if all test projects have been updated:

✅ Verification successful

Let me gather more detailed information to ensure we have the complete context:

This will help us verify not just the requested version but also the resolved version and content hash across all test projects.

---

✅ Verified: TestFramework version 3.0.49 is consistently updated across all test projects

All test projects (SocketTests, IPAddressTests, and NetworkHelperTests) have identical configurations for nanoFramework.TestFramework:

• Requested version: [3.0.49, 3.0.49]
• Resolved version: 3.0.49
• Content hash: +9xecBciJEhjSbNvnfET1nT3Zxvem9DMg8/yd30EOTHbccFhp5sjG5SO3CWVP/aLJib2I8KkjINiWXPjAuW7+w==

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that all test projects have the same TestFramework version

# Search for all packages.lock.json files in test projects
echo "Checking TestFramework versions in all test projects:"
fd packages.lock.json Tests/ --exec grep -A 2 '"nanoFramework.TestFramework"' {}

Length of output: 519

---

Script:

#!/bin/bash
# Get full context including resolved versions and content hashes
echo "Detailed TestFramework information from all test projects:"
fd packages.lock.json Tests/ --exec sh -c 'echo "=== {} ==="; grep -A 4 "nanoFramework.TestFramework" {}'

Length of output: 1129

---

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.