Update 3 NuGet dependencies

[nfbot]

Bumps nanoFramework.Iot.Device.Button from 1.2.696 to 1.2.718
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.696 to 1.2.718
Bumps nanoFramework.Iot.Device.Ssd13xx from 1.3.510 to 1.3.532

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Updated nanoFramework.Iot.Device.Button to version 1.2.718
  • Updated nanoFramework.Iot.Device.Buzzer to version 1.2.718
  • Updated nanoFramework.Iot.Device.Ssd13xx to version 1.3.532

[coderabbitai]

Walkthrough

This pull request involves updating dependency versions in packages.lock.json files for two nanoFramework projects: MagicBitTestApp and nanoFramework.MagicBit. The changes specifically target three IoT device libraries: nanoFramework.Iot.Device.Button, nanoFramework.Iot.Device.Buzzer, and nanoFramework.Iot.Device.Ssd13xx. The updates increment these libraries to newer versions, potentially introducing bug fixes or minor enhancements.

Changes

File	Changes
Tests/MagicBitTestApp/packages.lock.json	- Updated nanoFramework.Iot.Device.Button from 1.2.696 to 1.2.718 - Updated nanoFramework.Iot.Device.Buzzer from 1.2.696 to 1.2.718 - Updated nanoFramework.Iot.Device.Ssd13xx from 1.3.510 to 1.3.532
nanoFramework.MagicBit/packages.lock.json	- Updated nanoFramework.Iot.Device.Button from 1.2.696 to 1.2.718 - Updated nanoFramework.Iot.Device.Buzzer from 1.2.696 to 1.2.718 - Updated nanoFramework.Iot.Device.Ssd13xx from 1.3.510 to 1.3.532

Possibly related PRs

• Update 4 NuGet dependencies #184: Updates the same dependencies in the packages.lock.json file
• Update 6 NuGet dependencies #186: Updates similar dependencies with version increments
• Update 6 NuGet dependencies #205: Updates the same dependencies in the packages.lock.json file
• Update 1 NuGet dependencies #206: Updates a different dependency in the same project context

Suggested labels

CI: Publish Release

---

📜 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 fff19be and 635312e.

⛔ Files ignored due to path filters (5)

• Tests/MagicBitTestApp/MagicBitTestApp.nfproj is excluded by none and included by none
• Tests/MagicBitTestApp/packages.config is excluded by none and included by none
• nanoFramework.MagicBit.nuspec is excluded by none and included by none
• nanoFramework.MagicBit/nanoFramework.MagicBit.nfproj is excluded by none and included by none
• nanoFramework.MagicBit/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• Tests/MagicBitTestApp/packages.lock.json (2 hunks)
• nanoFramework.MagicBit/packages.lock.json (2 hunks)

🔇 Additional comments (2)

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

13-15: LGTM! Version updates match PR objectives.

The dependency updates are correctly implemented with matching version numbers and valid content hashes:

• nanoFramework.Iot.Device.Button: 1.2.718
• nanoFramework.Iot.Device.Buzzer: 1.2.718
• nanoFramework.Iot.Device.Ssd13xx: 1.3.532

Let's verify version consistency across the solution:

Also applies to: 19-21, 37-39

✅ Verification successful

✅ Version consistency verified across all packages.lock.json files

The verification confirms that both packages.lock.json files in the solution maintain consistent versions:

• nanoFramework.Iot.Device.Button: 1.2.718
• nanoFramework.Iot.Device.Buzzer: 1.2.718
• nanoFramework.Iot.Device.Ssd13xx: 1.3.532

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify version consistency across all packages.lock.json files
# Expected: All files should use the same versions for these packages

echo "Checking version consistency across packages.lock.json files..."
find . -name "packages.lock.json" -type f -exec sh -c '
    echo "\nFile: {}"
    grep -A 2 "\"nanoFramework.Iot.Device.Button\"" "{}" || true
    grep -A 2 "\"nanoFramework.Iot.Device.Buzzer\"" "{}" || true
    grep -A 2 "\"nanoFramework.Iot.Device.Ssd13xx\"" "{}" || true
' \;

Length of output: 1191

nanoFramework.MagicBit/packages.lock.json (1)

19-21: LGTM! Version updates are consistent with test project.

The dependency updates are correctly implemented and the content hashes match those in the test project, ensuring consistency across the solution:

• nanoFramework.Iot.Device.Button: 1.2.718
• nanoFramework.Iot.Device.Buzzer: 1.2.718
• nanoFramework.Iot.Device.Ssd13xx: 1.3.532

Also applies to: 25-27, 43-45

---

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.