Update 3 NuGet dependencies

[nfbot]

Bumps nanoFramework.Graphics.Core from 1.2.21 to 1.2.22
Bumps nanoFramework.Graphics from 1.2.21 to 1.2.22
Bumps nanoFramework.M5Core2 from 1.1.241 to 1.1.244

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• New Features

  • Updated dependencies for improved performance and stability, including nanoFramework.Graphics, nanoFramework.Graphics.Core, and nanoFramework.M5Core2.

• Bug Fixes

  • Enhanced compatibility and functionality through dependency upgrades.

[coderabbitai]

Walkthrough

The pull request updates the packages.lock.json files for both the devices/Ft6xx6x project and its samples directory. It reflects the upgrading of the nanoFramework.Graphics and nanoFramework.Graphics.Core packages from version 1.2.21 to 1.2.22, and the nanoFramework.M5Core2 package from version 1.1.241 to 1.1.244. The changes include updates to the requested, resolved, and contentHash fields, while all other dependencies remain unchanged.

Changes

File Path	Change Summary
devices/Ft6xx6x/packages.lock.json	- Updated nanoFramework.Graphics from 1.2.21 to 1.2.22
	- Updated nanoFramework.Graphics.Core from 1.2.21 to 1.2.22
	- Updated nanoFramework.M5Core2 from 1.1.241 to 1.1.244
devices/Ft6xx6x/samples/packages.lock.json	- Updated nanoFramework.Graphics from 1.2.21 to 1.2.22
	- Updated nanoFramework.Graphics.Core from 1.2.21 to 1.2.22
	- Updated nanoFramework.M5Core2 from 1.1.241 to 1.1.244

Possibly related PRs

• Update 4 NuGet dependencies #1140: This PR updates the nanoFramework.M5Core2 package from version 1.1.236 to 1.1.238, which is related to the main PR that updates nanoFramework.M5Core2 from 1.1.241 to 1.1.244.
• Update 4 NuGet dependencies #1153: This PR updates the nanoFramework.M5Core2 package from version 1.1.239 to 1.1.241, which is also related to the main PR that updates nanoFramework.M5Core2 from 1.1.241 to 1.1.244.
• Update 5 NuGet dependencies #1146: This PR updates the nanoFramework.Graphics.Core package from version 1.2.15 to 1.2.21, which is related to the main PR that updates nanoFramework.Graphics.Core from 1.2.21 to 1.2.22.
• Update 1 NuGet dependencies #1152: This PR updates the nanoFramework.Iot.Device.Common.GnssDevice package, which is not directly related to the main PR but indicates ongoing updates in the same ecosystem.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 2cb2c82 and 006a402.

⛔ Files ignored due to path filters (5)

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

📒 Files selected for processing (2)

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

🧰 Additional context used

🔇 Additional comments (5)

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

13-15: LGTM! Verify consistency across the repository.

The update to the nanoFramework.Graphics.Core package from version 1.2.21 to 1.2.22 has been correctly implemented in this packages.lock.json file. The requested and resolved versions, as well as the contentHash, have been updated appropriately.

To ensure consistency across the repository, please run the following script:

This script will help ensure that all packages.lock.json files in the repository have been consistently updated.

devices/Ft6xx6x/samples/packages.lock.json (4)

13-15: LGTM: nanoFramework.Graphics package update

The update of nanoFramework.Graphics from version 1.2.21 to 1.2.22 is consistent with the PR objectives. This minor version update likely includes bug fixes or small improvements.

---

19-21: LGTM: nanoFramework.Graphics.Core package update

The update of nanoFramework.Graphics.Core from version 1.2.21 to 1.2.22 is in line with the PR objectives. This minor version update is consistent with the nanoFramework.Graphics package update, which is good for maintaining compatibility between related packages.

---

Line range hint 1-214: Summary of package updates

This update includes minor version bumps for nanoFramework.Graphics and nanoFramework.Graphics.Core (1.2.21 to 1.2.22) and a patch version update for nanoFramework.M5Core2 (1.1.241 to 1.1.244). These changes are consistent with the PR objectives and likely include bug fixes and minor improvements.

Given the nature of these updates (minor and patch versions), the risk of breaking changes is low. However, it's always a good practice to run the project's test suite (if available) to ensure compatibility with the updated packages.

---

73-75: LGTM: nanoFramework.M5Core2 package update

The update of nanoFramework.M5Core2 from version 1.1.241 to 1.1.244 is consistent with the PR objectives. This patch version update likely includes bug fixes or minor improvements.

It might be beneficial to check the changelog for nanoFramework.M5Core2 to see if there are any notable changes or fixes in versions 1.1.242 through 1.1.244. You can use the following command to fetch the latest releases:

---

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.