Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.TestFramework from 2.1.112 to 2.1.113

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the dependency version of nanoFramework.TestFramework for improved stability and performance.

[coderabbitai]

Walkthrough

The changes involve an update to the packages.lock.json file in the Tests/System.IO.HashingTests project. The version of the nanoFramework.TestFramework dependency has been incremented from 2.1.112 to 2.1.113, accompanied by an updated content hash. Other dependencies in the file, specifically nanoFramework.CoreLibrary and nanoFramework.System.Text, remain unchanged.

Changes

File	Change Summary
Tests/System.IO.HashingTests/packages.lock.json	Updated nanoFramework.TestFramework version from 2.1.112 to 2.1.113 and modified content hash.

Possibly related PRs

• Update 1 NuGet dependencies #13: This PR updates the nanoFramework.TestFramework from version 2.1.107 to 2.1.111, which is directly related to the main PR's update from 2.1.112 to 2.1.113.
• Update 1 NuGet dependencies #14: This PR updates the nanoFramework.TestFramework from version 2.1.111 to 2.1.112, which is also directly related to the main PR's update to the next version.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6e75f5a and d73ebba.

⛔ Files ignored due to path filters (2)

• Tests/System.IO.HashingTests/System.IO.HashingTests.nfproj is excluded by none and included by none
• Tests/System.IO.HashingTests/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• Tests/System.IO.HashingTests/packages.lock.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (1)

Tests/System.IO.HashingTests/packages.lock.json (1)

19-21: LGTM! Dependency update looks correct.

The nanoFramework.TestFramework dependency has been successfully updated from version 2.1.112 to 2.1.113 as intended. This change is consistent with the PR objectives and affects only the targeted dependency.

To ensure the update was applied correctly across the project, you may want to run the following verification:

✅ Verification successful

Verification Successful: Dependency Update Complete.

The nanoFramework.TestFramework dependency has been successfully updated to version 2.1.113 across all relevant files. No references to the old version 2.1.112 were found.

• packages.lock.json
• packages.config
• System.IO.HashingTests.nfproj

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify that the TestFramework version is consistently updated across the project.

# Test: Search for any remaining references to the old version. Expect: No output.
rg --type-add 'proj:*.{csproj,props,targets}' --type proj '2\.1\.112'

# Test: Confirm the new version is used in project files. Expect: Matching lines with the new version.
rg --type-add 'proj:*.{csproj,props,targets}' --type proj '2\.1\.113'

Length of output: 441

---

Script:

#!/bin/bash
# Description: List all .csproj, .props, and .targets files in the repository to verify their existence.

fd --extension csproj --extension props --extension targets

Length of output: 61

---

Script:

#!/bin/bash
# Description: Search directly for the old and new TestFramework versions in .csproj, .props, and .targets files.

# Search for the old version
rg '2\.1\.112' --glob '*.csproj' --glob '*.props' --glob '*.targets'

# Search for the new version
rg '2\.1\.113' --glob '*.csproj' --glob '*.props' --glob '*.targets'

Length of output: 439

---

Script:

#!/bin/bash
# Description: Search for the old and new TestFramework versions across all files in the repository.

# Search for the old version
rg '2\.1\.112'

# Search for the new version
rg '2\.1\.113'

Length of output: 902

---

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.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud