Update 6 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.IO.FileSystem from 1.1.77 to 1.1.78
Bumps nanoFramework.System.IO.Ports from 1.1.116 to 1.1.119
Bumps nanoFramework.System.IO.Streams from 1.1.82 to 1.1.86
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.775 to 1.1.785
Bumps nanoFramework.System.Device.Wifi from 1.5.113 to 1.5.115
Bumps nanoFramework.System.Net from 1.11.25 to 1.11.27

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Upgraded various internal dependency versions across multiple test environments to ensure improved stability, performance, and maintainability for a smoother user experience.

[coderabbitai]

Walkthrough

This pull request updates dependency versions in various packages.lock.json files across multiple test and nanoFramework projects. The updates increment versions for dependencies such as nanoFramework.System.IO.FileSystem, nanoFramework.System.IO.Streams, nanoFramework.System.IO.Ports, along with others like nanoFramework.System.Wifi, nanoFramework.System.Net, and nanoFramework.Iot.Device.Chsc6540. Corresponding content hashes and other metadata are updated accordingly.

Changes

File Path(s)	Change Summary
Tests/FireTestApp/packages.lock.json	nanoFramework.System.IO.FileSystem: 1.1.77 → 1.1.78; nanoFramework.System.IO.Streams: 1.1.82 → 1.1.86
Tests/M5Core2TestApp/packages.lock.json	nanoFramework.System.Wifi: 1.5.113 → 1.5.115; nanoFramework.System.IO.FileSystem: 1.1.77 → 1.1.78; nanoFramework.System.IO.Ports: 1.1.116 → 1.1.119; nanoFramework.System.IO.Streams: 1.1.82 → 1.1.86; nanoFramework.System.Net: 1.11.25 → 1.11.27
Tests/M5CoreTestApp/packages.lock.json, nanoFramework.Fire/packages.lock.json, nanoFramework.M5Core/packages.lock.json, nanoFramework.M5Core2/packages.lock.json	nanoFramework.System.IO.FileSystem: 1.1.77 → 1.1.78; nanoFramework.System.IO.Ports: 1.1.116 → 1.1.119; nanoFramework.System.IO.Streams: 1.1.82 → 1.1.86
Tests/ToughTestApp/packages.lock.json	nanoFramework.Iot.Device.Chsc6540: 1.1.775 → 1.1.785; nanoFramework.System.Device.Wifi: 1.5.113 → 1.5.115; nanoFramework.System.IO.FileSystem: 1.1.77 → 1.1.78; nanoFramework.System.IO.Ports: 1.1.116 → 1.1.119; nanoFramework.System.IO.Streams: 1.1.82 → 1.1.86; nanoFramework.System.Net: 1.11.25 → 1.11.27
nanoFramework.Tough/packages.lock.json	nanoFramework.Iot.Device.Chsc6540: 1.1.775 → 1.1.785; nanoFramework.System.IO.FileSystem: 1.1.77 → 1.1.78; nanoFramework.System.IO.Ports: 1.1.116 → 1.1.119; nanoFramework.System.IO.Streams: 1.1.82 → 1.1.86

Possibly related PRs

• Update 3 NuGet dependencies #366: Updates to nanoFramework.System.IO.FileSystem and nanoFramework.System.IO.Streams reflect similar code-level dependency changes.
• Update 7 NuGet dependencies #343: The dependency version bumps mirror those in this PR, establishing a direct connection.
• Update 5 NuGet dependencies #350: Changes to nanoFramework.System.IO.FileSystem and nanoFramework.System.IO.Streams align closely with the modifications made here.

---

📜 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 47902af and 0a5cab0.

⛔ Files ignored due to path filters (20)

• Tests/FireTestApp/FireTestApp.nfproj is excluded by none and included by none
• Tests/FireTestApp/packages.config is excluded by none and included by none
• Tests/M5Core2TestApp/M5Core2TestApp.nfproj is excluded by none and included by none
• Tests/M5Core2TestApp/packages.config is excluded by none and included by none
• Tests/M5CoreTestApp/M5CoreTestApp.nfproj is excluded by none and included by none
• Tests/M5CoreTestApp/packages.config is excluded by none and included by none
• Tests/ToughTestApp/ToughTestApp.nfproj is excluded by none and included by none
• Tests/ToughTestApp/packages.config is excluded by none and included by none
• nanoFramework.Fire.nuspec is excluded by none and included by none
• nanoFramework.Fire/nanoFramework.Fire.nfproj is excluded by none and included by none
• nanoFramework.Fire/packages.config is excluded by none and included by none
• nanoFramework.M5Core.nuspec is excluded by none and included by none
• nanoFramework.M5Core/nanoFramework.M5Core.nfproj is excluded by none and included by none
• nanoFramework.M5Core/packages.config is excluded by none and included by none
• nanoFramework.M5Core2.nuspec is excluded by none and included by none
• nanoFramework.M5Core2/nanoFramework.M5Core2.nfproj is excluded by none and included by none
• nanoFramework.M5Core2/packages.config is excluded by none and included by none
• nanoFramework.Tough.nuspec is excluded by none and included by none
• nanoFramework.Tough/nanoFramework.Tough.nfproj is excluded by none and included by none
• nanoFramework.Tough/packages.config is excluded by none and included by none

📒 Files selected for processing (8)

• Tests/FireTestApp/packages.lock.json (1 hunks)
• Tests/M5Core2TestApp/packages.lock.json (3 hunks)
• Tests/M5CoreTestApp/packages.lock.json (1 hunks)
• Tests/ToughTestApp/packages.lock.json (2 hunks)
• nanoFramework.Fire/packages.lock.json (1 hunks)
• nanoFramework.M5Core/packages.lock.json (1 hunks)
• nanoFramework.M5Core2/packages.lock.json (1 hunks)
• nanoFramework.Tough/packages.lock.json (2 hunks)

✅ Files skipped from review due to trivial changes (2)

• Tests/FireTestApp/packages.lock.json
• Tests/M5CoreTestApp/packages.lock.json

🔇 Additional comments (25)

Tests/ToughTestApp/packages.lock.json (6)

29-33: Update for nanoFramework.Iot.Device.Chsc6540 version:
The dependency has been updated from 1.1.775 to 1.1.785 with a new content hash. This change is in line with the PR objectives.

---

77-81: Update for nanoFramework.System.Device.Wifi version:
The dependency version was updated from 1.5.113 to 1.5.115 and the content hash has changed accordingly. The change appears correct and consistent.

---

83-88: Update for nanoFramework.System.IO.FileSystem version:
The FileSystem dependency has been updated from 1.1.77 to 1.1.78. Both the requested/resolved versions and the content hash reflect the new version.

---

89-94: Update for nanoFramework.System.IO.Ports version:
The changes update the package from version 1.1.116 to 1.1.119. The updated content hash confirms the new version has been applied.

---

95-100: Update for nanoFramework.System.IO.Streams version:
The Streams dependency now reflects version 1.1.86 (updated from 1.1.82). The new content hash further confirms the update.

---

101-106: Update for nanoFramework.System.Net version:
The System.Net package has been updated from 1.11.25 to 1.11.27 while ensuring the content hash is recalculated.

nanoFramework.Tough/packages.lock.json (5)

35-40: Update for nanoFramework.Iot.Device.Chsc6540 version:
The requested and resolved versions have been updated to 1.1.785 with a new content hash. This reflects the intended dependency upgrade.

---

107-112: Update for nanoFramework.System.IO.FileSystem version:
The FileSystem dependency is now requested/resolved as 1.1.78. The updated content hash confirms the change.

---

113-118: Update for nanoFramework.System.IO.Ports version:
The dependency has been updated to version 1.1.119; both the version numbers and hash are updated accordingly.

---

119-124: Update for nanoFramework.System.IO.Streams version:
Requested and resolved versions have been changed to 1.1.86 with a matching updated content hash.

---

125-130: Update for nanoFramework.System.Net version:
The System.Net dependency now uses version 1.11.27. The content hash update confirms the new version.

nanoFramework.M5Core/packages.lock.json (3)

131-136: Update for nanoFramework.System.IO.FileSystem version:
The FileSystem dependency has been updated to 1.1.78 (from 1.1.77) with an updated content hash. This aligns with the global upgrade.

---

137-142: Update for nanoFramework.System.IO.Ports version:
The package has been revised from version 1.1.116 to 1.1.119. The updated hash confirms the change.

---

143-148: Update for nanoFramework.System.IO.Streams version:
The dependency version is now 1.1.86 (up from 1.1.82); the content hash has been refreshed correctly.

Tests/M5Core2TestApp/packages.lock.json (5)

131-136: Update for nanoFramework.System.Device.Wifi version:
The dependency has been updated to version 1.5.115 (from 1.5.113) with a new content hash. This update appears to be consistent with the other files.

---

143-148: Update for nanoFramework.System.IO.FileSystem version:
The FileSystem dependency is now set to version 1.1.78 with the appropriate updated hash.

---

149-154: Update for nanoFramework.System.IO.Ports version:
The Ports dependency has been updated to 1.1.119 with matching hash updates, in line with the global update.

---

155-160: Update for nanoFramework.System.IO.Streams version:
The Streams dependency now uses version 1.1.86; the update is confirmed by its new hash.

---

162-167: Update for nanoFramework.System.Net version:
The System.Net dependency has been updated from 1.11.25 to 1.11.27, with the new hash reflecting the upgrade.

nanoFramework.M5Core2/packages.lock.json (3)

151-153: Dependency Update: nanoFramework.System.IO.FileSystem

The dependency version has been updated from 1.1.77 to 1.1.78 along with an updated content hash. Verify that this update is backward compatible and that the new hash aligns with the package release.

---

157-159: Dependency Update: nanoFramework.System.IO.Ports

The version for nanoFramework.System.IO.Ports has been incremented from 1.1.116 to 1.1.119. The corresponding content hash has been updated accordingly. Please ensure that any behavioral changes between these versions have been tested.

---

163-165: Dependency Update: nanoFramework.System.IO.Streams

The version for nanoFramework.System.IO.Streams has been updated from 1.1.82 to 1.1.86 with a new content hash. Confirm that this update does not introduce regressions in IO stream handling and that it integrates smoothly with the rest of the system.

nanoFramework.Fire/packages.lock.json (3)

145-147: Updated "nanoFramework.System.IO.FileSystem" Dependency Version
The lock file now reflects the update from version 1.1.77 to 1.1.78. Please ensure that the updated content hash accurately corresponds to the new package version and is consistent with similar updates in other parts of the project.

---

151-153: Updated "nanoFramework.System.IO.Ports" Dependency Version
The dependency version has been bumped to 1.1.119, aligning with the broader upgrade initiative. It’s important to verify that the new content hash matches the updated package. Additionally, ensure that downstream consumers of this dependency are compatible with the new version.

---

157-159: Updated "nanoFramework.System.IO.Streams" Dependency Version
The lock file now uses version 1.1.86 instead of 1.1.82. Confirm that the content hash is correctly computed for this update and that the change harmonizes with similar updates made across the repository.

---

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.

[sonarqubecloud]

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 SonarQube Cloud