Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Iot.Device.Buzzer from 1.2.737 to 1.2.743

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Upgraded nanoFramework.Iot.Device.Buzzer package from version 1.2.737 to 1.2.743 in two project files
  • No other dependencies were modified

[coderabbitai]

Walkthrough

This pull request involves updating the nanoFramework.Iot.Device.Buzzer package version from 1.2.737 to 1.2.743 in two separate packages.lock.json files: one in the MagicBitTestApp and another in the nanoFramework.MagicBit project. The update appears to be a minor version upgrade that modifies the package's version specification and content hash while maintaining the same dependency structure.

Changes

File	Change Summary
Tests/MagicBitTestApp/packages.lock.json	Updated nanoFramework.Iot.Device.Buzzer package version from 1.2.737 to 1.2.743
nanoFramework.MagicBit/packages.lock.json	Updated nanoFramework.Iot.Device.Buzzer package version from 1.2.737 to 1.2.743

Possibly related PRs

• Update 6 NuGet dependencies #186: Updates nanoFramework.Iot.Device.Buzzer from version 1.2.536 to 1.2.570
• Update 5 NuGet dependencies #210: Updates nanoFramework.Iot.Device.Buzzer from version 1.2.718 to 1.2.737

---

📜 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 87f661e and 39c0ebf.

⛔ 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 (1 hunks)
• nanoFramework.MagicBit/packages.lock.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: nanoFramework / NuGets using latest version

🔇 Additional comments (2)

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

19-21: LGTM: Version update looks correct

The version update for nanoFramework.Iot.Device.Buzzer from 1.2.737 to 1.2.743 is properly specified with matching requested and resolved versions.

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

25-27: LGTM: Version update is consistent

The version update matches the test project, maintaining consistency across the solution. The content hash is correctly updated.

---

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.