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 stable releases, enhancing overall performance, reliability, and compatibility.

[coderabbitai]

Walkthrough

This pull request updates dependency version numbers in the packages.lock.json files for both the nanoFramework.Protobuf.Test.nano and nanoFramework.Protobuf projects. The updates include incrementing version numbers and corresponding content hashes for several dependencies. In the test project file, an additional dependency (nanoFramework.TestFramework) is also updated.

Changes

File	Change Summary
nanoFramework.Protobuf.Test.nano/.../packages.lock.json	Updated dependency versions for: nanoFramework.CoreLibrary (1.15.5 → 1.16.11), nanoFramework.System.Collections (1.5.45 → 1.5.59), nanoFramework.System.IO.Streams (1.1.77 → 1.1.86), nanoFramework.System.Text (1.3.1 → 1.3.16), and nanoFramework.TestFramework (3.0.49 → 3.0.67), with updated content hashes.
nanoFramework.Protobuf/.../packages.lock.json	Updated dependency versions for: nanoFramework.CoreLibrary (1.15.5 → 1.16.11), nanoFramework.System.Collections (1.5.45 → 1.5.59), nanoFramework.System.IO.Streams (1.1.77 → 1.1.86), and nanoFramework.System.Text (1.3.1 → 1.3.16), with updated content hashes.

Possibly related PRs

• Update 3 NuGet dependencies #12: This PR also involves dependency updates in the packages.lock.json files, specifically for nanoFramework.System.IO.Streams and nanoFramework.System.Text.

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 5652e0d.

⛔ 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 (3)

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

7-9:

Details

❓ Verification inconclusive

Verify compatibility with updated dependencies.

The updates include significant version changes, particularly:

• CoreLibrary: 1.15.5 -> 1.16.11 (major version change)
• System.Text: 1.3.1 -> 1.3.16 (15 versions ahead)

Please ensure there are no breaking changes that could affect the project.

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

---

🌐 Web query:

What are the breaking changes in nanoFramework.CoreLibrary 1.16.11 compared to 1.15.5?

💡 Result:

The primary breaking change in nanoFramework.CoreLibrary 1.16.11 compared to 1.15.5 involves native runtime compatibility requirements. Here's what developers need to know:

Mandatory Native Assembly Version Alignment

• Version 1.16.11 requires mscorlib v100.5.0.22 with specific checksums[1][3]
• Previous versions like 1.15.x used different native runtime versions (e.g., mscorlib v100.x.x.x with different checksums)[7][9]
• Mismatched versions will cause deployment failures due to checksum validation errors[7]

Binary Compatibility Considerations

• Interface changes between C# and native code components trigger new checksums[9]
• CoreLibrary updates often correlate with native assembly rebuilds requiring synchronized updates of:
  • nanoFramework.CoreLibrary NuGet
  • Device firmware/runtime image[7][9]

Key Impact Scenarios

	1.15.x Environment	1.16.x Upgrade Impact
Native Runtime	Older mscorlib	Requires reflashing devices with v100.5 runtime[7]
Existing Binaries	Compiled against older interfaces	May throw MissingMethodException[4]
Dependency Chains	Third-party libs using older CoreLibrary	Require updates to compatible versions[4]

Upgrade Requirements

1️⃣ Update all nanoFramework devices to runtime image supporting mscorlib v100.5
2️⃣ Recompile existing projects referencing CoreLibrary
3️⃣ Verify dependency tree for components requiring CoreLibrary ≤1.15.x

Note: The version jump from 1.15.x to 1.16.x indicates interface-level changes rather than minor fixes[9]. Always check package descriptions for exact native assembly requirements before deployment[3][7].

Citations:

• 1: https://www.nuget.org/packages/nanoFramework.CoreLibrary/1.16.11
• 2: https://www.nuget.org/packages/nanoFramework.CoreLibrary.NoReflection/
• 3: https://www.nuget.org/packages/nanoFramework.CoreLibrary
• 4: https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/breaking-changes
• 5: https://github.com/nanoframework/System.IO.Hashing/blob/main/nanoFramework.System.IO.Hashing.nuspec
• 6: https://learn.microsoft.com/en-us/dotnet/core/compatibility/8.0
• 7: https://docs.nanoframework.net/content/getting-started-guides/trouble-shooting-guide.html
• 8: https://github.com/nanoframework/nanoFramework.M5Stack/blob/main/nanoFramework.M5Core2.nuspec
• 9: https://docs.nanoframework.net/content/architecture/guide-version-checksums.html
• 10: https://nugetprodusnc-northcentralus-01.regional.azure-api.net/packages/nanoFramework.Fire/1.1.265

---

Updated Dependency Compatibility Verification

The update of nanoFramework.CoreLibrary from 1.15.5 to 1.16.11 introduces a critical breaking change due to native runtime compatibility requirements. Specifically, version 1.16.11 now mandates using mscorlib v100.5.0.22 along with matching checksums, which means devices might require a firmware/runtime update to avoid deployment failures (e.g., checksum validation errors or MissingMethodException). Additionally, the System.Text update from 1.3.1 to 1.3.16 should be reviewed to confirm no unintended issues arise, even though no explicit breaking changes are noted for it.

Please ensure:

• Device firmware and native runtime images are compatible with mscorlib v100.5.0.22.
• All dependent binaries and third-party libraries are recompiled or verified against the new CoreLibrary interface.
• The dependency tree (in all affected sections: lines 7-9, 13-15, 19-21, and 25-27) is examined for compatibility, particularly regarding native assembly version alignment.

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

7-9: LGTM! Dependencies are in sync with the main project.

The dependency versions match those in the main project file, which ensures consistency across the solution.

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

---

31-33:

Details

❓ Verification inconclusive

Verify compatibility with updated test framework.

The TestFramework update from 3.0.49 to 3.0.67 is significant (18 versions ahead). Please ensure there are no breaking changes that could affect the test suite.

---

🌐 Web query:

What are the breaking changes in nanoFramework.TestFramework 3.0.67 compared to 3.0.49?

💡 Result:

The provided search results do not explicitly list breaking changes between nanoFramework.TestFramework 3.0.67 and 3.0.49. However, general patterns from related .NET testing frameworks and nanoFramework development practices suggest potential areas of change:

Key Considerations:

1. Assertion Methods:
   New assertion methods or modifications to existing ones (e.g., stricter parameter validation) could break tests relying on older behavior[1][2].

2. Test Lifecycle Attributes:
   Changes to [TestClass], [TestMethod], or setup/cleanup attributes ([ClassInitialize], [TestCleanup]) might alter test execution order or requirements[2][6].

3. Reflection Handling:
   Updates to reflection logic (used for test discovery) could affect dynamically loaded tests or custom test runners[2][8].

4. Dependency Compatibility:
   Breaking changes in underlying .NET nanoFramework libraries (e.g., System.Collections, System.Reflection) might propagate to the test framework[3][4][6].

5. Exception Handling:
   Adjustments in exception types thrown by assertion failures or framework internals could disrupt error-catching logic[2][8].

Recommended Actions:

• Review the nanoFramework.TestFramework changelog directly in its GitHub repository (source 7) for version-specific notes.
• Test suites extensively after upgrading to identify runtime errors or behavioral shifts.
• Check for deprecated APIs flagged by compiler warnings when rebuilding tests against 3.0.67.

Without explicit release notes for these versions, caution and thorough testing are advised during upgrades.

Citations:

• 1: https://docs.nanoframework.net/content/unit-test/index.html
• 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: https://learn.microsoft.com/en-us/dotnet/core/compatibility/7.0
• 5: https://github.com/nanoframework/System.Collections/blob/main/CHANGELOG.md
• 6: https://nanoframework.net/laurent-ellerbach-a-year-deeply-in-net-nanoframework/
• 7: https://github.com/nanoframework/Home/releases
• 8: https://github.com/microsoft/testfx/blob/main/docs/Changelog.md
• 9: https://xunit.net/releases/visualstudio/3.0.0-pre.49
• 10: https://learn.microsoft.com/en-us/dotnet/core/compatibility/3.0

---

Subject: Verify nanoFramework.TestFramework Upgrade Compatibility

The update from 3.0.49 to 3.0.67 shows no explicit, documented breaking changes, but based on common patterns in nanoFramework and related testing frameworks, there are several areas that could be impacted:

• Assertion Methods: Potential modifications or stricter validations may affect tests relying on legacy behaviors.
• Test Lifecycle Attributes: Changes in attributes like [TestClass] and [TestMethod] might alter test discovery or execution order.
• Reflection Handling: Updates may influence custom test runners or dynamic test loading.
• Dependency Compatibility: Updates in underlying .NET nanoFramework libraries could propagate compatibility issues.
• Exception Handling: Adjustments in thrown exception types may affect error-catching logic.

Recommended Actions:

• Review the nanoFramework.TestFramework changelog on GitHub for any version-specific notes.
• Conduct thorough regression testing to ensure that all existing tests pass under the new version.
• Pay particular attention to any compiler warnings or deprecated API notices during the build.

---

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.