Update 3 NuGet dependencies

[nfbot]

Bumps nanoFramework.Benchmark from 1.0.106 to 1.0.107
Bumps nanoFramework.Logging from 1.1.155 to 1.1.156
Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.848 to 1.2.862

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated several core dependency libraries to their latest versions, which helps enhance overall performance, stability, and security. These routine improvements ensure the application continues to operate smoothly and reliably.

[coderabbitai]

Walkthrough

This change updates dependency versions in the packages.lock.json file for the nanoFramework.Hardware.Esp32.Rmt.Benchmarks project. Specifically, the versions for nanoFramework.Benchmark, nanoFramework.Logging, and nanoFramework.System.Diagnostics.Stopwatch have been incremented, with corresponding updates to their content hashes.

Changes

File(s)	Change Summary
nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json	- nanoFramework.Benchmark: 1.0.106 → 1.0.107 - nanoFramework.Logging: 1.1.155 → 1.1.156 - nanoFramework.System.Diagnostics.Stopwatch: 1.2.848 → 1.2.862 - Updated content hashes accordingly

Possibly related PRs

• Update 2 NuGet dependencies #82: Involves dependency updates for nanoFramework.Benchmark and nanoFramework.Logging with different version increments.
• Update 1 NuGet dependencies #75: Contains modifications to the nanoFramework.Logging package versions.
• Update 2 NuGet dependencies #79: Updates nanoFramework.Benchmark and nanoFramework.Logging dependencies, similar to the current changes.

Suggested reviewers

• josesimoes

---

📜 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 7d065f1 and 13c3931.

⛔ Files ignored due to path filters (2)

• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/nanoFramework.Hardware.Esp32.Rmt.Benchmarks.nfproj is excluded by none and included by none
• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json (3 hunks)

🔇 Additional comments (3)

nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json (3)

7-9: Dependency Version Update: nanoFramework.Benchmark
The updated dependency version from 1.0.106 to 1.0.107 is properly reflected by the new "requested" and "resolved" values, and the accompanying content hash has been updated. Ensure that the new version has been validated against your usage to avoid any unintended regressions.

---

19-21: Dependency Version Update: nanoFramework.Logging
The updated version for nanoFramework.Logging (from 1.1.155 to 1.1.156) is correctly applied here. The "requested" and "resolved" entries and the content hash have all been updated consistently. It’s advisable to run your test suite to confirm that the update doesn’t introduce any incompatibilities.

---

37-39: Dependency Version Update: nanoFramework.System.Diagnostics.Stopwatch
The dependency update for nanoFramework.System.Diagnostics.Stopwatch is well-executed. The version bump to 1.2.862 is accurately updated in both "requested" and "resolved" fields, along with the changed content hash. Please verify that these changes are in line with your project’s compatibility requirements.

---

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 plan to trigger planning for file edits and PR creation.
• @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