Update 5 NuGet dependencies

[nfbot]

Bumps nanoFramework.CoreLibrary from 1.15.5 to 1.16.11
Bumps nanoFramework.System.Collections from 1.5.45 to 1.5.59
Bumps nanoFramework.System.IO.Streams from 1.1.77 to 1.1.86
Bumps nanoFramework.System.Text from 1.3.1 to 1.3.16
Bumps nanoFramework.TestFramework from 3.0.49 to 3.0.67

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Upgraded several core dependencies to their latest versions to enhance performance, reliability, and overall compatibility.

[coderabbitai]

Walkthrough

The pull request updates dependency version specifications in two packages.lock.json files. For both files, the dependency versions for nanoFramework.CoreLibrary, nanoFramework.System.Collections, nanoFramework.System.IO.Streams, and nanoFramework.System.Text are upgraded, and the corresponding content hashes are updated. Additionally, the nanoFramework.Protobuf.Test.nano file updates the version of nanoFramework.TestFramework from 3.0.49 to 3.0.67.

Changes

File(s)	Change Summary
nanoFramework.Protobuf.Test.nano/.../packages.lock.json	Updated dependency versions: nanoFramework.CoreLibrary from 1.15.5 to 1.16.11; nanoFramework.System.Collections from 1.5.45 to 1.5.59; nanoFramework.System.IO.Streams from 1.1.77 to 1.1.86; nanoFramework.System.Text from 1.3.1 to 1.3.16; nanoFramework.TestFramework from 3.0.49 to 3.0.67. Updated content hash values for each dependency.
nanoFramework.Protobuf/.../packages.lock.json	Updated dependency versions: nanoFramework.CoreLibrary from 1.15.5 to 1.16.11; nanoFramework.System.Collections from 1.5.45 to 1.5.59; nanoFramework.System.IO.Streams from 1.1.77 to 1.1.86; nanoFramework.System.Text from 1.3.1 to 1.3.16. Updated content hash values for each dependency.

Possibly related PRs

• Update 3 NuGet dependencies #12: Involves similar updates to the dependencies nanoFramework.System.IO.Streams and nanoFramework.System.Text in corresponding packages.lock.json files.

Suggested labels

CI: Publish Release

---

📜 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 18bf9ab and d1cd106.

⛔ Files ignored due to path filters (5)

• nanoFramework.Protobuf.Test.nano/nanoFramework.Protobuf.Test.Nano.nfproj is excluded by none and included by none
• nanoFramework.Protobuf.Test.nano/packages.config is excluded by none and included by none
• nanoFramework.Protobuf.nuspec is excluded by none and included by none
• nanoFramework.Protobuf/nanoFramework.Protobuf.nfproj is excluded by none and included by none
• nanoFramework.Protobuf/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• nanoFramework.Protobuf.Test.nano/packages.lock.json (1 hunks)
• nanoFramework.Protobuf/packages.lock.json (1 hunks)

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

• GitHub Check: nanoFramework / NuGets using latest version

🔇 Additional comments (2)

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

7-9:

Details

✅ Verification successful

LGTM! Version updates look consistent.

The version updates follow semantic versioning with appropriate version ranges. Most updates are patch version bumps, except for CoreLibrary which has a minor version bump.

Let's verify if there are any breaking changes in the CoreLibrary update:

Also applies to: 13-15, 19-21, 25-27

---

🌐 Web query:

Are there any breaking changes in nanoFramework.CoreLibrary between versions 1.15.5 and 1.16.11?

💡 Result:

Between nanoFramework.CoreLibrary versions 1.15.5 (released November 9, 2023) and 1.16.11 (released February 3, 2025), there are no explicitly documented breaking API changes in the provided sources[1][7]. However:

Key Observations

Version Compatibility

• The BUILD_VERSION must match between nanoCLR firmware and CoreLibrary[4]. Mismatches trigger deployment errors like:

  Found assemblies mismatches when checking for deployment pre-check
  

• Version 0.x.y.z indicates preview status[7], while 1.x.y.z releases are stable[1].

Potential Breaking Change Indicators

• A major checksum change occurred at v100.x.x.x, requiring manual NuGet package version updates[7]
• Dependency requirements changed:
  • Version 1.16.x requires mscorlib v100.5.0.22[1]

Testing Requirements
New code must:

• Pass all existing unit tests without regressions[3]
• Include tests covering all methods/properties/exceptions[3]
• Support both BCL flavors (with/without Reflection)[5]

Upgrade Recommendations

# Always verify BUILD_VERSION matches firmware
dotnet add package nanoFramework.CoreLibrary --version 1.16.11

While no direct API breaks are documented between these versions[1][7], always test upgrades thoroughly due to:

• Native code interoperability requirements[3]
• Strict assembly version matching rules[4][8]
• Potential implicit behavior changes from dependency updates[2][9]

For complete safety: check native method signatures in corlib_native.* files after upgrading[3].

Citations:

• 1: https://www.nuget.org/packages/nanoFramework.CoreLibrary/1.16.11
• 2: https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/breaking-changes
• 3: https://docs.nanoframework.net/content/contributing/developer-guide.html
• 4: https://docs.nanoframework.net/content/building/build-instructions.html
• 5: https://github.com/nanoframework/CoreLibrary
• 6: https://github.com/nanoframework/nanoFramework.ResourceManager/blob/main/CHANGELOG.md
• 7: https://docs.nanoframework.net/content/architecture/guide-version-checksums.html
• 8: https://docs.nanoframework.net/content/getting-started-guides/trouble-shooting-guide.html
• 9: https://blog.devmobile.co.nz/2022/03/05/net-nanoframework-valuechanged/
• 10: https://www.nuget.org/packages/nanoFramework.Graphics.Gc9A01

---

LGTM! Version updates are consistent and adhere to semantic versioning.

All dependency updates in packages.lock.json are locked to exact versions and show appropriate patch bumps—with the exception of the minor bump in CoreLibrary. Our verification confirms that between nanoFramework.CoreLibrary versions 1.15.5 and 1.16.11 there are no explicitly documented breaking API changes. That said, please ensure that:

• The BUILD_VERSION in nanoCLR firmware matches the CoreLibrary version to avoid deployment mismatches.
• Comprehensive testing is performed to catch potential issues stemming from native code interoperability and dependency requirements (e.g., ensuring compatibility with mscorlib v100.5.0.22).

nanoFramework.Protobuf.Test.nano/packages.lock.json (1)

7-9:

Details

✅ Verification successful

LGTM! Version updates are consistent with the main project.

The version updates in the test project match those in the main project, with an additional update to TestFramework. All updates follow semantic versioning with appropriate version ranges.

Let's verify if there are any breaking changes in the TestFramework update:

Also applies to: 13-15, 19-21, 25-27, 31-33

---

🌐 Web query:

Are there any breaking changes in nanoFramework.TestFramework between versions 3.0.49 and 3.0.67?

💡 Result:

Between versions 3.0.49 and 3.0.67 of nanoFramework.TestFramework, there are no documented breaking changes in the available search results[1][2][5][10]. The framework maintains backward compatibility with its core testing attributes (TestClass, TestMethod) and assertion patterns[2][5]. Key implementation details remain consistent:

• Test discovery uses reflection with attribute-based recognition[2][7]
• Assertion methods follow familiar patterns (Assert.Equal, Assert.Throws)[2][5]
• Test execution flow maintains setup/cleanup attributes[5]

The architecture documentation shows no fundamental changes to test deployment or versioning mechanisms during this period[9]. While general .NET breaking changes occurred in other components (like MSTest v3 parameter limits[4] and ASP.NET Core API removals[6]), these don't directly impact nanoFramework.TestFramework's implementation.

For production use, always verify release notes specific to your target version range, as undocumented edge cases might exist in niche scenarios[10].

Citations:

• 1: https://nanoframework.net/laurent-ellerbach-a-year-deeply-in-net-nanoframework/
• 2: https://devblogs.microsoft.com/dotnet/show-dotnet-build-your-own-unit-test-platform-the-true-story-of-net-nanoframework/
• 3: https://learn.microsoft.com/en-us/dotnet/core/compatibility/8.0
• 4: MSTest v3 Breaking Changes microsoft/testfx#1274
• 5: https://docs.nanoframework.net/content/unit-test/index.html
• 6: https://learn.microsoft.com/en-us/dotnet/core/compatibility/3.0
• 7: https://docs.nanoframework.net/content/architecture/unit-test.html
• 8: https://xunit.net/releases/visualstudio/3.0.0-pre.49
• 9: https://docs.nanoframework.net/content/architecture/deployment.html
• 10: https://github.com/nanoframework/nanoFramework.TestFramework

---

Verified Dependency Updates and TestFramework Compatibility

The updated dependency versions in nanoFramework.Protobuf.Test.nano/packages.lock.json are consistent with the main project. The following updates have been applied:

• CoreLibrary: 1.15.5 → 1.16.11
• System.Collections: 1.5.45 → 1.5.59
• System.IO.Streams: 1.1.77 → 1.1.86
• System.Text: 1.3.1 → 1.3.16
• TestFramework: 3.0.49 → 3.0.67

A web query confirmed that there are no documented breaking changes in nanoFramework.TestFramework between versions 3.0.49 and 3.0.67. Additionally, the snippet locations (lines 7-9, and similarly at 13-15, 19-21, 25-27, 31-33) show correctly locked version ranges with matching requested and resolved versions.

These updates follow semantic versioning and no further action is required.

---

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.