Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated nanoFramework.System.IO.Streams dependency from version 1.1.59 to 1.1.75 across multiple project files
  • Added nanoFramework.TestFramework version 3.0.49 to NetworkHelperTests project

[coderabbitai]

Walkthrough

This pull request focuses on updating the nanoFramework.System.IO.Streams dependency version from 1.1.59 to 1.1.75 across multiple project test and library directories. The changes are consistent across Tests/IPAddressTests, Tests/NetworkHelperTests, Tests/SocketTests, and nanoFramework.System.Net directories, involving updates to the packages.lock.json files. The updates include modifying the requested, resolved, and contentHash fields to reflect the new dependency version.

Changes

File	Change Summary
Tests/IPAddressTests/packages.lock.json	Updated nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75
Tests/NetworkHelperTests/packages.lock.json	Updated nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75 Added nanoFramework.TestFramework version 3.0.49
Tests/SocketTests/packages.lock.json	Updated nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75
nanoFramework.System.Net/packages.lock.json	Updated nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75

Possibly related PRs

• Update 1 NuGet dependencies #316: Updates nanoFramework.TestFramework dependency in similar packages.lock.json files
• Update 1 NuGet dependencies #317: Similar dependency update for nanoFramework.TestFramework
• Update 1 NuGet dependencies #320: Continues updating nanoFramework.TestFramework in the same project files

---

📜 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 a44e2db and 3827d87.

⛔ Files ignored due to path filters (9)

• Tests/IPAddressTests/IPAddressTests.nfproj is excluded by none and included by none
• Tests/IPAddressTests/packages.config is excluded by none and included by none
• Tests/NetworkHelperTests/NetworkHelperTests.nfproj is excluded by none and included by none
• Tests/NetworkHelperTests/packages.config is excluded by none and included by none
• Tests/SocketTests/SocketTests.nfproj is excluded by none and included by none
• Tests/SocketTests/packages.config is excluded by none and included by none
• nanoFramework.System.Net.nuspec is excluded by none and included by none
• nanoFramework.System.Net/System.Net.nfproj is excluded by none and included by none
• nanoFramework.System.Net/packages.config is excluded by none and included by none

📒 Files selected for processing (4)

• Tests/IPAddressTests/packages.lock.json (1 hunks)
• Tests/NetworkHelperTests/packages.lock.json (1 hunks)
• Tests/SocketTests/packages.lock.json (1 hunks)
• nanoFramework.System.Net/packages.lock.json (1 hunks)

🔇 Additional comments (4)

Tests/SocketTests/packages.lock.json (1)

13-15: LGTM! Version update is consistent with PR objective.

The update of nanoFramework.System.IO.Streams to version 1.1.75 is properly specified with exact version range and matching content hash.

Tests/IPAddressTests/packages.lock.json (1)

13-15: LGTM! Version update is consistent across test projects.

The dependency update matches exactly with SocketTests/packages.lock.json, maintaining consistency across the test suite.

Tests/NetworkHelperTests/packages.lock.json (1)

13-15: LGTM! Version update is consistent and dependencies are compatible.

The nanoFramework.System.IO.Streams update matches other test projects. The presence of additional dependencies (System.Threading) is unchanged and compatible with the updated version.

Let's verify version compatibility across the dependencies:

✅ Verification successful

Version 1.1.75 of System.IO.Streams is consistently used across the codebase

The verification confirms that version 1.1.75 of nanoFramework.System.IO.Streams is consistently referenced across:

• All test projects (NetworkHelperTests, SocketTests, IPAddressTests)
• Main project (nanoFramework.System.Net)
• NuGet package specification

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for any known compatibility issues between the updated version and other dependencies

# Search for any compatibility requirements or issues in the repository
rg -i "system\.io\.streams.*1\.1\.75.*compatibility"

# Check if there are any specific version requirements in build configurations
fd -e props -e csproj | xargs rg "System\.IO\.Streams"

Length of output: 2317

nanoFramework.System.Net/packages.lock.json (1)

19-21: LGTM! Version update looks correct.

The dependency update for nanoFramework.System.IO.Streams from 1.1.59 to 1.1.75 is properly reflected in the lock file with corresponding contentHash update.

Let's verify the changelog for any breaking changes:

✅ Verification successful

Version update is safe - no breaking changes found

The release notes for version 1.1.75 show only an enhancement that fixes MemoryStream.CanWrite behavior to allow read-only mode (PR #67). This is a non-breaking change that improves functionality. The update from 1.1.59 to 1.1.75 appears to be safe.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changelog and release notes for the version update
# to ensure there are no breaking changes between 1.1.59 and 1.1.75

# Fetch release information from GitHub
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/System.IO.Streams/releases \
  --jq 'map(select(.tag_name >= "v1.1.59" and .tag_name <= "v1.1.75")) | map({version: .tag_name, body: .body})'

Length of output: 1299

---

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.