Update 20 NuGet dependencies

[nfbot]

Bumps nanoFramework.CoreLibrary from 1.15.5 to 1.16.1
Bumps nanoFramework.Graphics.Core from 1.2.22 to 1.2.33
Bumps nanoFramework.Iot.Device.Multiplexing from 1.2.715 to 1.2.751
Bumps nanoFramework.Iot.Device.ShiftRegister from 1.2.716 to 1.2.752
Bumps nanoFramework.ResourceManager from 1.2.19 to 1.2.28
Bumps nanoFramework.Runtime.Events from 1.11.18 to 1.11.26
Bumps nanoFramework.Runtime.Native from 1.7.1 to 1.7.7
Bumps nanoFramework.System.Collections from 1.5.45 to 1.5.56
Bumps nanoFramework.System.Device.Gpio from 1.1.41 to 1.1.52
Bumps nanoFramework.System.Device.I2c from 1.1.16 to 1.1.25
Bumps nanoFramework.System.Device.Spi from 1.3.52 to 1.3.71
Bumps nanoFramework.System.Diagnostics.Stopwatch from 1.2.693 to 1.2.751
Bumps nanoFramework.System.IO.FileSystem from 1.1.69 to 1.1.74
Bumps nanoFramework.System.IO.Streams from 1.1.77 to 1.1.82
Bumps nanoFramework.System.Math from 1.5.43 to 1.5.86
Bumps nanoFramework.System.Runtime from 1.0.27 to 1.0.28
Bumps nanoFramework.System.Text from 1.3.1 to 1.3.9
Bumps nanoFramework.System.Threading from 1.1.32 to 1.1.45
Bumps nanoFramework.Hardware.Esp32 from 1.6.23 to 1.6.28
Bumps nanoFramework.Iot.Device.Pcx857x from 1.2.737 to 1.2.755

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated multiple nanoFramework dependencies to their latest versions across core libraries, system components, and device-specific packages.
  • Upgraded versions for libraries related to core functionality, device interaction, and system operations.

[coderabbitai]

Walkthrough

This pull request involves updating dependency versions for the devices/CharacterLcd project and its samples. The changes systematically update multiple nanoFramework library dependencies to their latest versions across two packages.lock.json files. The updates span core libraries, device-specific libraries, system libraries, and runtime components, ensuring the project uses the most recent available library versions.

Changes

File	Change Summary
devices/CharacterLcd/packages.lock.json	Updated 17 nanoFramework dependencies, including core libraries, device libraries, system libraries, and runtime components
devices/CharacterLcd/samples/packages.lock.json	Updated 19 nanoFramework dependencies, with additional updates to nanoFramework.Hardware.Esp32 and nanoFramework.Iot.Device.Pcx857x

Possibly related PRs

• Update 3 NuGet dependencies #1224: Updates nanoFramework.System.Text dependency
• Update 10 NuGet dependencies #1242: Updates nanoFramework.CoreLibrary version
• Update 61 NuGet dependencies #1247: Updates multiple core library and runtime dependencies

Suggested labels

CI: Publish Release, Type: dependencies

---

📜 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 a7d0a7b and 2acbe6b.

⛔ Files ignored due to path filters (6)

• devices/CharacterLcd/CharacterLcd.nfproj is excluded by none and included by none
• devices/CharacterLcd/CharacterLcd.nuspec is excluded by none and included by none
• devices/CharacterLcd/CharacterLcd.sln is excluded by none and included by none
• devices/CharacterLcd/packages.config is excluded by none and included by none
• devices/CharacterLcd/samples/CharacterLcd.Samples.nfproj is excluded by none and included by none
• devices/CharacterLcd/samples/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• devices/CharacterLcd/packages.lock.json (1 hunks)
• devices/CharacterLcd/samples/packages.lock.json (1 hunks)

🔇 Additional comments (2)

devices/CharacterLcd/packages.lock.json (1)

7-105: LGTM! Version updates look consistent.

All package version updates are properly locked and resolved to their specified versions. The updates are minor version increments, which suggests backward compatibility is maintained.

Let's verify if there are any known security advisories for these updated packages:

✅ Verification successful

Package updates verified - no security concerns found

Security check completed for core nanoFramework packages. No known vulnerabilities found in the GitHub Security Advisory Database for the updated versions.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for security advisories for the updated packages

# Check for security advisories for core packages
for package in "nanoFramework.CoreLibrary" "nanoFramework.Runtime.Native" "nanoFramework.System.IO.FileSystem"
do
  echo "Checking $package..."
  gh api graphql -f query='{
    securityVulnerabilities(first: 5, ecosystem: NUGET, package: "'$package'") {
      nodes {
        advisory {
          summary
          severity
          publishedAt
        }
        vulnerableVersionRange
        firstPatchedVersion {
          identifier
        }
      }
    }
  }'
done

Length of output: 1791

devices/CharacterLcd/samples/packages.lock.json (1)

7-111: LGTM! Sample project versions are in sync with the main project.

The package versions in the samples project are consistent with the main project, and the additional sample-specific packages follow the same update pattern.

---

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.