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 for improved functionality and performance.

[coderabbitai]

Walkthrough

The pull request updates the packages.lock.json file for the nanoFramework.TestFramework dependency, changing its version from 3.0.42 to 3.0.47. This includes a modification to the content hash corresponding to the new version. No other dependencies or elements within the file have been altered.

Changes

File	Change Summary
Tests/MathUnitTests/packages.lock.json	Updated nanoFramework.TestFramework version from 3.0.42 to 3.0.47 and modified content hash.

Possibly related PRs

• Update 1 NuGet dependencies #186: This PR updates the nanoFramework.TestFramework dependency in the same packages.lock.json file, changing the version from 2.1.113 to 3.0.42, which is directly related to the version change in the main PR from 3.0.42 to 3.0.47.

Warning

Rate limit exceeded

@nfbot has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 12 minutes and 13 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 2496d5e and 359736e.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 2496d5e and 359736e.

⛔ Files ignored due to path filters (2)

• Tests/MathUnitTests/MathUnitTests.nfproj is excluded by none and included by none
• Tests/MathUnitTests/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• Tests/MathUnitTests/packages.lock.json (1 hunks)

🔇 Additional comments (1)

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

13-15: LGTM! Version update looks correct.

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

Let's verify the version and check for any breaking changes:

✅ Verification successful

Version update is safe and up-to-date

The update to nanoFramework.TestFramework v3.0.47 is confirmed to be the latest available version. The changes between v3.0.42 and v3.0.47 consist of:

• Updates to debugger library and tools
• Test adapter project rework
• Dependencies updates (CliWrap)

No breaking changes were identified in the release notes, making this a safe update.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the latest version and changelog for nanoFramework.TestFramework

# Check if this is the latest version available
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nanoframework.TestFramework/releases | \
  jq -r '.[0].tag_name'

# Look for any breaking changes or important notes in recent releases
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nanoframework.TestFramework/releases | \
  jq -r '.[] | select(.tag_name >= "v3.0.42" and .tag_name <= "v3.0.47") | "\n## " + .tag_name + "\n" + .body'

Length of output: 1746

---

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.

[sonarqubecloud]

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