Update 2 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.IO.FileSystem from 1.1.82 to 1.1.83
Bumps nanoFramework.Hardware.Esp32 from 1.6.32 to 1.6.33

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Upgraded several internal dependencies to their latest versions for increased reliability, improved performance, and enhanced stability.
  • These behind‑the‑scenes updates ensure that the application remains robust and up‑to‑date with current standards, contributing to a smoother user experience while providing ongoing critical maintenance for long‑term success.

[coderabbitai]

Walkthrough

This pull request updates dependency versions in two packages.lock.json files. In the Tests unit, the nanoFramework.Hardware.Esp32 dependency is upgraded from version 1.6.32 to 1.6.33, and the nanoFramework.System.IO.FileSystem dependency is updated from version 1.1.82 to 1.1.83. The same FileSystem dependency update is also applied in the nanoFramework.Logging.Stream package, with corresponding changes to the requested, resolved, and content hash values.

Changes

File(s)	Change Summary
Tests/.../packages.lock.json, nanoFramework.Logging.Stream/packages.lock.json	Updated nanoFramework.System.IO.FileSystem from 1.1.82 to 1.1.83 with modifications to the requested version, resolved version, and contentHash.
Tests/.../packages.lock.json	Updated nanoFramework.Hardware.Esp32 from 1.6.32 to 1.6.33, including its associated version details.

Possibly related PRs

• Update 6 NuGet dependencies #277: Addresses updates to the nanoFramework.System.IO.FileSystem dependency, aligning with changes made in this PR.
• Update 1 NuGet dependencies #231: Involves modifications to the packages.lock.json file, specifically updating the nanoFramework.System.IO.FileSystem dependency version.
• Update 1 NuGet dependencies #244: Pertains to updates of the nanoFramework.Hardware.Esp32 dependency in a similar context within a packages.lock.json file.

---

📜 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 2835358 and 92ce489.

⛔ Files ignored due to path filters (5)

• Tests/UnitTestDebugLogging/UnitTestDebugLogging.nfproj is excluded by none and included by none
• Tests/UnitTestDebugLogging/packages.config is excluded by none and included by none
• nanoFramework.Logging.Stream.nuspec is excluded by none and included by none
• nanoFramework.Logging.Stream/nanoFramework.Logging.Stream.nfproj is excluded by none and included by none
• nanoFramework.Logging.Stream/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• Tests/UnitTestDebugLogging/packages.lock.json (2 hunks)
• nanoFramework.Logging.Stream/packages.lock.json (1 hunks)

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

• GitHub Check: nanoFramework / NuGets using latest version

🔇 Additional comments (3)

Tests/UnitTestDebugLogging/packages.lock.json (2)

13-15: Dependency Update for nanoFramework.Hardware.Esp32
The version for nanoFramework.Hardware.Esp32 has been bumped to 1.6.33 with updated requested, resolved, and contentHash fields. This change is consistent with the intended dependency update. Please ensure dependent projects or tests have been verified against this new version.

---

31-33: Dependency Update for nanoFramework.System.IO.FileSystem
The dependency version for nanoFramework.System.IO.FileSystem has been updated to 1.1.83. The updates in the requested, resolved, and contentHash fields are correctly applied. This update is consistent with similar changes in the nanoFramework.Logging.Stream package; please confirm overall compatibility with all consuming projects.

nanoFramework.Logging.Stream/packages.lock.json (1)

19-21: Dependency Update for nanoFramework.System.IO.FileSystem
The nanoFramework.System.IO.FileSystem dependency in this file is updated to 1.1.83 with corresponding changes to requested, resolved, and contentHash. This mirrors the update applied in the Tests unit, ensuring consistency. Please verify that this update integrates smoothly with the rest of the package dependencies.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @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.