Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.TestFramework from 3.0.69 to 3.0.73

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Upgraded the testing framework dependency to a newer version across multiple test areas to improve internal test performance and consistency.

[coderabbitai]

Walkthrough

The pull request updates the nanoFramework.TestFramework dependency version in multiple test projects’ packages.lock.json files. In each file, both the requested and resolved versions have been changed from 3.0.69 to 3.0.73, and the associated content hash has been updated to reflect this new version.

Changes

File(s)	Change Summary
Tests/…/packages.lock.json (IPAddressTests, NetworkHelperTests, SocketTests)	Updated nanoFramework.TestFramework dependency from version 3.0.69 to 3.0.73. This includes changes in both the requested/resolved versions and the content hash.

Possibly related PRs

• Update 1 NuGet dependencies #320: Involves a dependency update for nanoFramework.TestFramework, but targets version upgrade from 2.1.104 to 2.1.107.
• Update 1 NuGet dependencies #344: Updates the same dependency from 3.0.66 to 3.0.67, showing a similar code-level change.
• Update 1 NuGet dependencies #331: Focuses on modifying the dependency version from 3.0.47 to 3.0.49, indicating a related change in the dependency management.

---

📜 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 11620b2 and 7c064eb.

⛔ 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)

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

• GitHub Check: System.Net (Build_Library)

🔇 Additional comments (3)

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

25-27: Dependency Version Update Confirmed:

The update for the nanoFramework.TestFramework dependency correctly changes the requested version to [3.0.73, 3.0.73], updates the resolved version to 3.0.73, and revises the contentHash accordingly. This update is consistent and aligns with the intended NuGet upgrade.

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

25-27: Consistent Dependency Upgrade:

The nanoFramework.TestFramework dependency in this file has been updated from version 3.0.69 to 3.0.73 with the corresponding content hash change. The modifications are clear and maintain consistency with similar updates in other test modules.

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

31-33: Accurate Dependency Revision:

The dependency update for nanoFramework.TestFramework here is correctly applied with the new version [3.0.73, 3.0.73] in the requested field, the resolved version set to 3.0.73, and an updated contentHash. This consistency across multiple test projects ensures that the upgrade is reliable.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.