Update 6 NuGet dependencies

[nfbot]

Bumps nanoFramework.CoreLibrary from 1.15.5 to 1.16.1
Bumps nanoFramework.Runtime.Events from 1.11.18 to 1.11.26
Bumps nanoFramework.System.IO.Streams from 1.1.77 to 1.1.82
Bumps nanoFramework.System.Text from 1.3.1 to 1.3.9
Bumps nanoFramework.TestFramework from 3.0.49 to 3.0.57

[version update]

Remove dependency of nanoFramework.System.Runtime

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Updated nanoFramework.CoreLibrary to version 1.16.1
  • Updated nanoFramework.System.IO.Streams to version 1.1.82
  • Updated nanoFramework.System.Text to version 1.3.9
  • Updated nanoFramework.TestFramework to version 3.0.57
  • Updated nanoFramework.Runtime.Events to version 1.11.26
  • Removed nanoFramework.System.Runtime dependency

[coderabbitai]

Walkthrough

This pull request focuses on updating dependency versions in two packages.lock.json files for the System.IO.FileSystem project. The changes involve incrementing versions for several nanoFramework libraries in both the unit tests and main project configurations. The updates include version bumps for nanoFramework.CoreLibrary, nanoFramework.System.IO.Streams, nanoFramework.System.Text, and nanoFramework.TestFramework. Additionally, the nanoFramework.System.Runtime dependency was removed from the main project's package lock file.

Changes

File	Changes
System.IO.FileSystem.UnitTests/packages.lock.json	- Updated nanoFramework.CoreLibrary from 1.15.5 to 1.16.1 - Updated nanoFramework.System.IO.Streams from 1.1.77 to 1.1.82 - Updated nanoFramework.System.Text from 1.3.1 to 1.3.9 - Updated nanoFramework.TestFramework from 3.0.49 to 3.0.57
System.IO.FileSystem/packages.lock.json	- Updated nanoFramework.CoreLibrary from 1.15.5 to 1.16.1 - Updated nanoFramework.Runtime.Events from 1.11.18 to 1.11.26 - Updated nanoFramework.System.IO.Streams from 1.1.77 to 1.1.82 - Updated nanoFramework.System.Text from 1.3.1 to 1.3.9 - Removed nanoFramework.System.Runtime dependency

Possibly related PRs

• Update 1 NuGet dependencies #103: Updates nanoFramework.TestFramework in System.IO.FileSystem.UnitTests/packages.lock.json
• Update 1 NuGet dependencies #120: Updates Nerdbank.GitVersioning dependency in System.IO.FileSystem/packages.lock.json
• Update 1 NuGet dependencies #123: Updates Nerdbank.GitVersioning dependency in System.IO.FileSystem/packages.lock.json

---

📜 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 c34e8c9 and 91fb883.

⛔ Files ignored due to path filters (5)

• System.IO.FileSystem.UnitTests/System.IO.FileSystem.UnitTests.nfproj is excluded by none and included by none
• System.IO.FileSystem.UnitTests/packages.config is excluded by none and included by none
• System.IO.FileSystem/System.IO.FileSystem.nfproj is excluded by none and included by none
• System.IO.FileSystem/packages.config is excluded by none and included by none
• nanoFramework.System.IO.FileSystem.nuspec is excluded by none and included by none

📒 Files selected for processing (2)

• System.IO.FileSystem.UnitTests/packages.lock.json (1 hunks)
• System.IO.FileSystem/packages.lock.json (1 hunks)

🔇 Additional comments (3)

System.IO.FileSystem.UnitTests/packages.lock.json (1)

7-27: LGTM! Version updates look safe.

All dependency updates are minor or patch version increments, which should maintain backward compatibility:

• CoreLibrary: 1.15.5 → 1.16.1 (minor)
• System.IO.Streams: 1.1.77 → 1.1.82 (patch)
• System.Text: 1.3.1 → 1.3.9 (patch)
• TestFramework: 3.0.49 → 3.0.57 (patch)

Let's verify these are the latest stable versions:

✅ Verification successful

✓ All package versions are up to date

Verified that all package versions in packages.lock.json match the latest stable versions available on NuGet.org.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check NuGet.org for latest stable versions of the packages
for package in "nanoFramework.CoreLibrary" "nanoFramework.System.IO.Streams" "nanoFramework.System.Text" "nanoFramework.TestFramework"; do
    echo "Checking $package..."
    curl -s "https://api.nuget.org/v3/registration5-semver1/$package/index.json" | jq -r '.items[0].upper'
done

Length of output: 1619

---

Script:

#!/bin/bash
# Check NuGet.org for latest stable versions using the v3 API search endpoint
for package in "nanoFramework.CoreLibrary" "nanoFramework.System.IO.Streams" "nanoFramework.System.Text" "nanoFramework.TestFramework"; do
    echo "Checking $package..."
    curl -s "https://azuresearch-usnc.nuget.org/query?q=$package&prerelease=false&semVerLevel=2.0.0" | \
    jq -r --arg pkg "$package" '.data[] | select(.id==$pkg) | .version'
done

Length of output: 1750

System.IO.FileSystem/packages.lock.json (2)

7-27: LGTM! Version updates look safe and consistent.

All dependency updates are minor or patch version increments, maintaining backward compatibility:

• CoreLibrary: 1.15.5 → 1.16.1 (minor)
• Runtime.Events: 1.11.18 → 1.11.26 (patch)
• System.IO.Streams: 1.1.77 → 1.1.82 (patch)
• System.Text: 1.3.1 → 1.3.9 (patch)

Versions are consistent with the UnitTests project where applicable.

---

Line range hint 1-35: Verify removal of nanoFramework.System.Runtime dependency.

The System.Runtime package has been removed from the dependencies. Let's verify this won't cause any issues.

✅ Verification successful

The removal of nanoFramework.System.Runtime dependency appears safe

The codebase only uses basic runtime types (CompilerServices, InteropServices) which are typically provided by CoreLibrary, and there are no direct references to any nanoFramework.System.Runtime specific types.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for any remaining System.Runtime usage in the codebase
echo "Searching for System.Runtime namespace usage..."
rg "using.*System\.Runtime" --type csharp

echo "Searching for explicit System.Runtime types..."
rg "System\.Runtime\.[a-zA-Z]+" --type csharp

echo "Checking if any remaining files reference the removed package..."
find . -name "*.csproj" -exec grep -l "nanoFramework.System.Runtime" {} \;

Length of output: 2326

---

Script:

#!/bin/bash
# Check the CoreLibrary package contents for these types
echo "Searching for CompilerServices and InteropServices in CoreLibrary..."
rg -l "namespace.*System\.Runtime\.(CompilerServices|InteropServices)" -g "CoreLibrary*"

# Also check for any direct usage of types from nanoFramework.System.Runtime
echo "Checking for any direct usage of nanoFramework.System.Runtime types..."
rg "nanoFramework\.System\.Runtime\.[a-zA-Z]+" --type csharp

Length of output: 600

---

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

[josesimoes]

@nfbot updatedependencies all