Update 5 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.Runtime from 1.0.27 to 1.0.28
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]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated dependency versions:
    • nanoFramework.CoreLibrary to 1.16.1
    • nanoFramework.Runtime.Events to 1.11.26
    • nanoFramework.System.Runtime to 1.0.28
    • nanoFramework.System.Text to 1.3.9

[coderabbitai]

Walkthrough

This pull request involves updating dependency versions in two packages.lock.json files for the System.IO.FileSystem project. The changes primarily focus on incrementing versions for several nanoFramework dependencies, including CoreLibrary, Runtime.Events, System.Runtime, and System.Text. These updates suggest a routine maintenance process of keeping project dependencies current with their latest released versions.

Changes

File	Changes
System.IO.FileSystem.UnitTests/packages.lock.json	- Updated nanoFramework.CoreLibrary from 1.15.5 to 1.16.1 - 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.Runtime from 1.0.27 to 1.0.28 - Updated nanoFramework.System.Text from 1.3.1 to 1.3.9

Possibly related PRs

• Update 1 NuGet dependencies #103: Updates nanoFramework.TestFramework from 3.0.49 to 3.0.57
• Update 1 NuGet dependencies #114: Updates nanoFramework.TestFramework from 2.1.111 to 2.1.112
• Update 1 NuGet dependencies #117: Updates nanoFramework.TestFramework from 2.1.113 to 3.0.42

---

📜 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 6776017.

⛔ 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 (2 hunks)
• System.IO.FileSystem/packages.lock.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: nanoFramework / NuGets using latest version

🔇 Additional comments (6)

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

7-9: Verify breaking changes in CoreLibrary 1.16.1

The update from 1.15.5 to 1.16.1 might include breaking changes. Let's verify the changelog.

✅ Verification successful

CoreLibrary 1.16.1 update is safe to proceed

The update from 1.15.5 to 1.16.1 contains only additive features, bug fixes, and internal improvements. No breaking changes were identified in the release notes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in nanoFramework.CoreLibrary

# Fetch release notes between versions
gh release view --repo nanoframework/CoreLibrary v1.16.1 
gh release view --repo nanoframework/CoreLibrary v1.15.5

Length of output: 2219

---

19-21: Verify breaking changes in System.Text 1.3.9

The update from 1.3.1 to 1.3.9 is a significant version jump. Let's verify the changelog.

✅ Verification successful

No breaking changes detected in System.Text 1.3.9

The version update from 1.3.1 to 1.3.9 consists only of dependency updates and improvements to StringBuilder. The release notes don't indicate any breaking changes.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in nanoFramework.System.Text

# Fetch release notes between versions
gh release view --repo nanoframework/System.Text v1.3.9
gh release view --repo nanoframework/System.Text v1.3.1

Length of output: 1488

---

Script:

#!/bin/bash
# Get the actual code changes between versions
gh api repos/nanoframework/System.Text/compare/v1.3.1...v1.3.9 | jq -r '.files[] | select(.filename | endswith(".cs")) | "\n=== \(.filename) ===\n\(.patch)"'

Length of output: 159

---

25-27: Verify breaking changes in TestFramework 3.0.57

The update from 3.0.49 to 3.0.57 is a significant version jump. Let's verify the changelog.

✅ Verification successful

TestFramework update 3.0.49 → 3.0.57 is safe to proceed

All changes between versions are maintenance-related (dependency updates and internal improvements) with no breaking changes or API modifications.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in nanoFramework.TestFramework

# Fetch release notes between versions
gh release view --repo nanoframework/nanoFramework.TestFramework v3.0.57
gh release view --repo nanoframework/nanoFramework.TestFramework v3.0.49

Length of output: 1432

---

Script:

#!/bin/bash
# Description: Fetch all releases between v3.0.49 and v3.0.57

# Get all releases and filter for the version range we're interested in
gh api \
  -H "Accept: application/vnd.github+json" \
  repos/nanoframework/nanoFramework.TestFramework/releases \
  --paginate \
  --jq '.[] | select(.tag_name | startswith("v3.0.")) | select(.tag_name >= "v3.0.49" and .tag_name <= "v3.0.57") | {tag: .tag_name, body: .body}'

Length of output: 1469

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

31-33: Version consistency verified for System.Text

The System.Text version 1.3.9 matches between the main project and test project.

---

13-15: Verify breaking changes in Runtime.Events 1.11.26

The update from 1.11.18 to 1.11.26 is a significant version jump. Let's verify the changelog.

✅ Verification successful

Update to Runtime.Events 1.11.26 is safe

The version update only contains routine dependency updates with no breaking changes or API modifications.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in nanoFramework.Runtime.Events

# Fetch release notes between versions
gh release view --repo nanoframework/nanoFramework.Runtime.Events v1.11.26
gh release view --repo nanoframework/nanoFramework.Runtime.Events v1.11.18

Length of output: 1601

---

Script:

#!/bin/bash
# Description: Check changelog for breaking changes in nanoFramework.Runtime.Events

# Fetch changelog content
curl -s https://raw.githubusercontent.com/nanoframework/nanoFramework.Runtime.Events/main/CHANGELOG.md

Length of output: 42558

---

25-27: Verify breaking changes in System.Runtime 1.0.28

The update from 1.0.27 to 1.0.28 is a minor version bump. Let's verify the changelog.

✅ Verification successful

No breaking changes in System.Runtime 1.0.28 update

The version bump is safe. The changes involve moving compiler attributes to mscorlib as part of a planned deprecation. The migration is backward compatible, allowing consumers to transition at their convenience.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for breaking changes in nanoFramework.System.Runtime

# Fetch release notes between versions
gh release view --repo nanoframework/nanoFramework.System.Runtime v1.0.28
gh release view --repo nanoframework/nanoFramework.System.Runtime v1.0.27

Length of output: 1221

---

Script:

#!/bin/bash
# Description: Check PR #10 details and changes

# Fetch PR details
gh pr view 10 --repo nanoframework/nanoFramework.System.Runtime

# Get PR diff
gh pr diff 10 --repo nanoframework/nanoFramework.System.Runtime

Length of output: 19159

---

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.

[josesimoes]

@nfbot updatedependencies