Update 16 NuGet dependencies

[nfbot]

Bumps nanoFramework.Iot.Device.Button from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.696 to 1.2.737
Bumps Nerdbank.GitVersioning from 3.7.112 to 3.7.115
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.718 to 1.2.743
Bumps UnitsNet.nanoFramework.Temperature from 5.65.0 to 5.66.0
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.718 to 1.2.743
Bumps nanoFramework.Iot.Device.ePaper from 1.0.558 to 1.0.573
Bumps nanoFramework.Iot.Device.Rtc from 1.2.718 to 1.2.743
Bumps UnitsNet.nanoFramework.Frequency from 5.65.0 to 5.66.0
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.704 to 1.2.737
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.718 to 1.2.743
Bumps UnitsNet.nanoFramework.ElectricCurrent from 5.65.0 to 5.66.0
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.718 to 1.2.743
Bumps UnitsNet.nanoFramework.ElectricPotential from 5.65.0 to 5.66.0
Bumps UnitsNet.nanoFramework.Power from 5.65.0 to 5.66.0
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.696 to 1.1.737

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Updated multiple nanoFramework IoT device dependencies across various projects
  • Upgraded UnitsNet dependencies from version 5.65.0 to 5.66.0
  • Updated Nerdbank.GitVersioning from version 3.7.112 to 3.7.115
  • Versions range from 1.1.737 to 1.2.743 for different device-specific libraries

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (9)

• nanoFramework.AtomLite/nanoFramework.AtomLite.nfproj is excluded by none and included by none
• nanoFramework.AtomMatrix/nanoFramework.AtomMatrix.nfproj is excluded by none and included by none
• nanoFramework.CoreInk/nanoFramework.CoreInk.nfproj is excluded by none and included by none
• nanoFramework.Fire/nanoFramework.Fire.nfproj is excluded by none and included by none
• nanoFramework.M5Core/nanoFramework.M5Core.nfproj is excluded by none and included by none
• nanoFramework.M5Core2/nanoFramework.M5Core2.nfproj is excluded by none and included by none
• nanoFramework.M5StickC/nanoFramework.M5StickC.nfproj is excluded by none and included by none
• nanoFramework.M5StickCPlus/nanoFramework.M5StickCPlus.nfproj is excluded by none and included by none
• nanoFramework.Tough/nanoFramework.Tough.nfproj is excluded by none and included by none

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request involves updating dependency versions across multiple packages.lock.json files in various nanoFramework projects. The updates primarily target dependencies like nanoFramework.Iot.Device.*, UnitsNet.nanoFramework.*, and Nerdbank.GitVersioning. The changes increment package versions to newer releases, ranging from minor version bumps to updates in device-specific libraries and measurement unit packages.

Changes

File	Change Summary
Tests/*/packages.lock.json	Updated multiple dependencies: nanoFramework.Iot.Device.* from versions like 1.2.718 to 1.2.737/1.2.743, UnitsNet.nanoFramework.* from 5.65.0 to 5.66.0
nanoFramework.*/packages.lock.json	Similar dependency updates across different project configurations, including Nerdbank.GitVersioning from 3.7.112 to 3.7.115

Possibly related PRs

• Update 5 NuGet dependencies #331: Updates to nanoFramework.Iot.Device.Button and nanoFramework.Iot.Device.Ws28xx.Esp32
• Update 14 NuGet dependencies #333: Similar dependency updates matching the main PR
• Update 4 NuGet dependencies #334: Update to nanoFramework.Iot.Device.Ws28xx.Esp32

Suggested labels

CI: Publish Release

Suggested reviewers

• Ellerbach

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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