Update 2 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.IO.Streams from 1.1.94 to 1.1.96
Bumps nanoFramework.TestFramework from 3.0.75 to 3.0.77

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated package dependencies to newer versions for improved compatibility and stability.

[coderabbitai]

Walkthrough

This change updates package dependencies in three separate packages.lock.json files across the repository. Specifically, the version of nanoFramework.System.IO.Streams is incremented from 1.1.94 to 1.1.96 in all affected files. Additionally, in the test project, the nanoFramework.TestFramework package is updated from 3.0.75 to 3.0.77. No source code or public API changes are introduced, and no other dependencies are altered.

Changes

File(s)	Change Summary
nanoFramework.Json.Benchmark/packages.lock.json, nanoFramework.Json/packages.lock.json	Updated nanoFramework.System.IO.Streams package version from 1.1.94 to 1.1.96.
nanoFramework.Json.Test/packages.lock.json	Updated nanoFramework.System.IO.Streams from 1.1.94 to 1.1.96 and nanoFramework.TestFramework from 3.0.75 to 3.0.77.

Possibly related PRs

• Update 7 NuGet dependencies #400: Updates nanoFramework.System.IO.Streams from 1.1.86 to 1.1.88, indicating a similar dependency version bump.
• Update 2 NuGet dependencies #410: Updates nanoFramework.System.IO.Streams from 1.1.89 to 1.1.91, also involving a related dependency update.

---

📜 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 2cfb073 and 59a31c9.

⛔ Files ignored due to path filters (7)

• nanoFramework.Json.Benchmark/nanoFramework.Json.Benchmark.nfproj is excluded by none and included by none
• nanoFramework.Json.Benchmark/packages.config is excluded by none and included by none
• nanoFramework.Json.Test/nanoFramework.Json.Test.nfproj is excluded by none and included by none
• nanoFramework.Json.Test/packages.config is excluded by none and included by none
• nanoFramework.Json.nuspec is excluded by none and included by none
• nanoFramework.Json/nanoFramework.Json.nfproj is excluded by none and included by none
• nanoFramework.Json/packages.config is excluded by none and included by none

📒 Files selected for processing (3)

• nanoFramework.Json.Benchmark/packages.lock.json (1 hunks)
• nanoFramework.Json.Test/packages.lock.json (2 hunks)
• nanoFramework.Json/packages.lock.json (1 hunks)

🔇 Additional comments (4)

nanoFramework.Json.Benchmark/packages.lock.json (1)

43-45: Update nanoFramework.System.IO.Streams to 1.1.96
The requested and resolved versions along with the content hash have been correctly bumped from 1.1.94 to 1.1.96. This aligns with the PR’s objective to keep dependencies in sync across projects.

nanoFramework.Json/packages.lock.json (1)

19-21: Synchronize nanoFramework.System.IO.Streams version to 1.1.96
The version and content hash have been correctly updated in this lock file to match the benchmark and test projects. No other dependencies were affected.

nanoFramework.Json.Test/packages.lock.json (2)

19-21: Bump nanoFramework.System.IO.Streams in test project
The test project’s streams package is now properly aligned at version 1.1.96, consistent with the other modules.

---

31-33: Upgrade nanoFramework.TestFramework to 3.0.77
The test framework dependency has been correctly updated from 3.0.75 to 3.0.77, reflecting the PR’s intent to update NuGet packages.

---

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.