Update 3 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.IO.Ports from 1.1.131 to 1.1.132
Bumps nanoFramework.System.IO.Streams from 1.1.94 to 1.1.96
Bumps nanoFramework.System.Net from 1.11.42 to 1.11.43

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated several internal dependencies to newer versions for improved stability and compatibility across multiple projects. No changes to user-facing features or functionality.

[coderabbitai]

Caution

Review failed

The pull request is closed.

## Walkthrough

This change updates the `packages.lock.json` files across multiple projects to reference newer versions of several nanoFramework packages. Specifically, the updates include bumping `nanoFramework.System.IO.Ports` from 1.1.131 to 1.1.132, `nanoFramework.System.IO.Streams` from 1.1.94 to 1.1.96, and `nanoFramework.System.Net` from 1.11.42 to 1.11.43 where applicable. The updates adjust the requested and resolved versions, as well as the content hashes, to reflect these new package versions. No changes were made to code or public API declarations.

## Changes

| Files                                                                                  | Change Summary                                                                                                     |
|----------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------|
| Tests/FireTestApp/packages.lock.json                                                   | Updated `nanoFramework.System.IO.Streams` from 1.1.94 to 1.1.96.                                                  |
| Tests/M5Core2TestApp/packages.lock.json, Tests/ToughTestApp/packages.lock.json         | Updated `nanoFramework.System.IO.Ports` (1.1.131 → 1.1.132), `nanoFramework.System.IO.Streams` (1.1.94 → 1.1.96), and `nanoFramework.System.Net` (1.11.42 → 1.11.43). |
| Tests/M5CoreTestApp/packages.lock.json, nanoFramework.Fire/packages.lock.json,         |
| nanoFramework.M5Core/packages.lock.json, nanoFramework.M5Core2/packages.lock.json,     |
| nanoFramework.Tough/packages.lock.json                                                 | Updated `nanoFramework.System.IO.Ports` from 1.1.131 to 1.1.132 and `nanoFramework.System.IO.Streams` from 1.1.94 to 1.1.96. |

## Possibly related PRs

- nanoframework/nanoFramework.M5Stack#405: Updates the version of nanoFramework.System.IO.Streams from 1.1.94 to 1.1.96 in multiple package lock files, closely matching this PR's dependency changes.
- nanoframework/nanoFramework.M5Stack#396: Updates nanoFramework.System.IO.Streams but to a different version (1.1.88 → 1.1.89), showing a similar pattern of dependency updates.
- nanoframework/nanoFramework.M5Stack#385: Updates nanoFramework.System.IO.Streams from 1.1.82 to 1.1.86, related through similar dependency version bumping.

## Suggested labels

`CI: Publish Release`

## Suggested reviewers

- AdrianSoundy

---

📜 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 6074070 and 1f8253c.

⛔ 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 (2 hunks)
• Tests/M5CoreTestApp/packages.lock.json (1 hunks)
• Tests/ToughTestApp/packages.lock.json (1 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 (1 hunks)

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[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