Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.TestFramework from 3.0.42 to 3.0.47

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the nanoFramework.TestFramework dependency version from 3.0.42 to 3.0.47.

[coderabbitai]

Walkthrough

The pull request updates the packages.lock.json file to change the version of the nanoFramework.TestFramework dependency from 3.0.42 to 3.0.47. This update includes a new content hash for the dependency, reflecting the updated version. No other dependencies or configurations were modified in this change.

Changes

File Path	Change Summary
Tests/System.IO.HashingTests/packages.lock.json	Updated nanoFramework.TestFramework from 3.0.42 to 3.0.47, including a new content hash.

Possibly related PRs

• Update 1 NuGet dependencies #7: Updates the nanoFramework.TestFramework version from 2.1.94 to 2.1.100, indicating a similar dependency update process.
• Update 1 NuGet dependencies #8: Changes the nanoFramework.TestFramework version from 2.1.100 to 2.1.104, showing a continuous update of the same dependency.
• Update 1 NuGet dependencies #10: Updates the nanoFramework.TestFramework from 2.1.104 to 2.1.107, reflecting ongoing version management for the same package.
• Update 1 NuGet dependencies #13: Updates the nanoFramework.TestFramework from 2.1.107 to 2.1.111, maintaining the same pattern of version updates.
• Update 1 NuGet dependencies #14: Changes the nanoFramework.TestFramework version from 2.1.111 to 2.1.112, indicating a direct relationship with the main PR's focus on version updates.
• Update 1 NuGet dependencies #15: Updates the nanoFramework.TestFramework from 2.1.112 to 2.1.113, continuing the trend of version increments for the same dependency.
• Update 1 NuGet dependencies #17: Changes the nanoFramework.TestFramework version from 2.1.113 to 3.0.42, which is a significant update aligning with the main PR's update to 3.0.47.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1220c60 and e1d3cda.

⛔ 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 comments (1)

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

19-21: LGTM! Version update looks correct.

The update of nanoFramework.TestFramework from 3.0.42 to 3.0.47 is consistent with semantic versioning (patch update) and includes the corresponding content hash update.

Let's verify the package version and integrity:

✅ Verification successful

Version 3.0.47 is verified and available

The GitHub API results confirm that version 3.0.47 of nanoFramework.TestFramework was officially released on November 27, 2024. The release is stable (not marked as prerelease or draft) and includes the corresponding NuGet package. No open issues were found related to this version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the NuGet package version exists and check for any known issues
# Note: Using GitHub API to check releases and issues mentioning this version

# Check for the specific version in repository releases
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nanoFramework.TestFramework/releases | \
  jq '.[] | select(.tag_name | contains("v3.0.47"))'

# Check for any issues mentioning this version
gh api \
  -H "Accept: application/vnd.github+json" \
  search/issues \
  -f q='repo:nanoframework/nanoFramework.TestFramework "3.0.47" is:issue state:open' | \
  jq '.items[] | {title: .title, url: .html_url}'

Length of output: 4610

---

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 SonarQube Cloud