Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Device.Bluetooth from 1.1.83 to 1.1.84

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• New Features

  • Updated the Bluetooth dependency to enhance performance and compatibility across BLE Keyboard and Mouse samples.

• Bug Fixes

  • Resolved issues related to the previous Bluetooth version, improving overall functionality.

[coderabbitai]

Walkthrough

The changes involve updates to the packages.lock.json files for three projects: Samples/BLEKeyboardSample, Samples/BLEMouseSample, and nanoFramework.Bluetooth.Hid. The version of the nanoFramework.Device.Bluetooth dependency has been incremented from 1.1.83 to 1.1.84, with corresponding modifications to the requested, resolved, and contentHash fields for this dependency across all three projects. No other dependencies were altered.

Changes

File Path	Change Summary
Samples/BLEKeyboardSample/packages.lock.json	Updated nanoFramework.Device.Bluetooth from 1.1.83 to 1.1.84
Samples/BLEMouseSample/packages.lock.json	Updated nanoFramework.Device.Bluetooth from 1.1.83 to 1.1.84
nanoFramework.Bluetooth.Hid/packages.lock.json	Updated nanoFramework.Device.Bluetooth from 1.1.83 to 1.1.84

Possibly related PRs

• Update 2 NuGet dependencies #11: This PR updates the nanoFramework.Device.Bluetooth dependency from 1.1.65 to 1.1.75, which is related as it involves changes to the same dependency in the packages.lock.json files.
• Update 2 NuGet dependencies #18: This PR updates the nanoFramework.Device.Bluetooth dependency from 1.1.75 to 1.1.83, which is directly related as it involves changes to the same dependency in the same files as the main PR.

Suggested labels

CI: Publish Release

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 6ffce90 and 2b84f3c.

⛔ Files ignored due to path filters (7)

• Samples/BLEKeyboardSample/BLEKeyboardSample.nfproj is excluded by none and included by none
• Samples/BLEKeyboardSample/packages.config is excluded by none and included by none
• Samples/BLEMouseSample/BLEMouseSample.nfproj is excluded by none and included by none
• Samples/BLEMouseSample/packages.config is excluded by none and included by none
• nanoFramework.Bluetooth.Hid.nuspec is excluded by none and included by none
• nanoFramework.Bluetooth.Hid/nanoFramework.Bluetooth.Hid.nfproj is excluded by none and included by none
• nanoFramework.Bluetooth.Hid/packages.config is excluded by none and included by none

📒 Files selected for processing (3)

• Samples/BLEKeyboardSample/packages.lock.json (1 hunks)
• Samples/BLEMouseSample/packages.lock.json (1 hunks)
• nanoFramework.Bluetooth.Hid/packages.lock.json (1 hunks)

🧰 Additional context used

🔇 Additional comments (3)

Samples/BLEMouseSample/packages.lock.json (1)

13-15: LGTM: NuGet dependency update looks correct.

The update of the nanoFramework.Device.Bluetooth package from version 1.1.83 to 1.1.84 has been implemented correctly:

1. The requested and resolved fields have been consistently updated to "1.1.84".
2. The contentHash has been updated, which is expected with a new version.
3. No other unintended changes were made to the file.

This minor version update (1.1.83 to 1.1.84) suggests a backwards-compatible change, which should not introduce breaking changes to the project. However, it's always a good practice to test the project thoroughly after dependency updates.

To ensure this update is consistent across the project, let's verify other packages.lock.json files:

✅ Verification successful

✅ Dependency Update Verified Successfully

The nanoFramework.Device.Bluetooth package has been consistently updated to version 1.1.84 across all relevant packages.lock.json files. No issues were found during the verification process.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the version update of nanoFramework.Device.Bluetooth across all packages.lock.json files

# Test: Search for nanoFramework.Device.Bluetooth in all packages.lock.json files
# Expect: All occurrences should show version 1.1.84
rg --type json -C 5 '"nanoFramework\.Device\.Bluetooth"' $(fd -g '*packages.lock.json')

Length of output: 3149

Samples/BLEKeyboardSample/packages.lock.json (1)

13-15: LGTM: Package update correctly implemented

The nanoFramework.Device.Bluetooth package has been successfully updated from version 1.1.83 to 1.1.84. The changes are consistent across all relevant fields (requested, resolved, and contentHash). This update aligns perfectly with the PR objectives.

To ensure this update is consistent across all relevant files, let's run the following verification script:

This script will help us confirm that the update has been applied consistently across all relevant files in the project.

nanoFramework.Bluetooth.Hid/packages.lock.json (1)

13-15: LGTM: Dependency update looks good.

The update of nanoFramework.Device.Bluetooth from version 1.1.83 to 1.1.84 is consistent with the PR objectives. The change includes updates to the requested version, resolved version, and content hash, which is expected for a dependency update.

Let's verify if this change is consistent across all affected files:

✅ Verification successful

: Dependency update is consistent across all package.lock.json files.

All instances of nanoFramework.Device.Bluetooth have been updated to version 1.1.84 as expected. No inconsistencies found across the reviewed files.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the consistency of the nanoFramework.Device.Bluetooth version update across all package lock files.

# Test: Search for nanoFramework.Device.Bluetooth in all package lock files
# Expect: All occurrences should show version 1.1.84
rg --type json '"nanoFramework\.Device\.Bluetooth"' -A 3 $(fd -e json packages.lock.json)

Length of output: 1184

---

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.

[sonarcloud]

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 SonarCloud