Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.Net from 1.11.43 to 1.11.46

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated internal dependencies to enhance system stability and performance.

[coderabbitai]

Walkthrough

Updated nanoFramework.System.Net dependency from version 1.11.43 to 1.11.46 in the UdpClient packages lock file, including corresponding updates to requested, resolved, and content hash values.

Changes

Cohort / File(s)	Summary
Dependency Version Update nanoFramework.System.Net.Sockets.UdpClient/packages.lock.json	Bumped nanoFramework.System.Net from 1.11.43 to 1.11.46; updated associated requested, resolved, and contentHash values

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Update 1 NuGet dependencies' accurately describes the main change: updating a NuGet dependency version in the packages.lock.json file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch nfbot/update-dependencies/a2ae35a8-809d-48e1-b245-e2d05cb285bf

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b34946d and dd9eebe.

⛔ Files ignored due to path filters (3)

• nanoFramework.System.Net.Sockets.UdpClient.nuspec is excluded by none and included by none
• nanoFramework.System.Net.Sockets.UdpClient/nanoFramework.System.Net.Sockets.UdpClient.nfproj is excluded by none and included by none
• nanoFramework.System.Net.Sockets.UdpClient/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.System.Net.Sockets.UdpClient/packages.lock.json (1 hunks)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Dependency update looks good; verify no security issues or breaking changes.

The nanoFramework.System.Net dependency has been correctly updated from 1.11.43 to 1.11.46 with consistent version pinning and an appropriately updated content hash. The patch-level bump suggests backward compatibility, but please verify there are no security advisories or breaking changes in this version range.

---

🌐 Web query:

What are the changes between nanoFramework.System.Net version 1.11.43 and 1.11.46? Are there any security advisories?

💡 Result:

Short answer: There are no published differences because nanoFramework.System.Net version 1.11.46 does not appear to be published on NuGet — the latest listed release is 1.11.43 (published 2025-04-24). [1]

What I checked

• NuGet package versions list for nanoFramework.System.Net shows 1.11.43 as the latest published version (1.11.43 — 2025‑04‑24); no 1.11.46 entry is present. [1]
• I found no vendor security advisory specifically calling out a vulnerability or CVE for nanoFramework.System.Net (public nanoFramework posts describe ongoing TLS/mbedTLS upgrades and network security improvements, but not a security advisory against 1.11.43→1.11.46). [2][3]

Conclusion / recommendation

• If you meant a different package/version, or you have a private build (1.11.46) you want compared, share the release notes or the package — I can compare the assemblies/changelogs.
• If you’re concerned about security: upgrade to the latest published nanoFramework releases and follow the project’s TLS/mbedTLS migration notes; open-source advisories would be posted by the project on their site/GitHub. [2][3]

Sources

1. nuget.org package page and versions list for nanoFramework.System.Net.
2. .NET nanoFramework blog posts on network/TLS updates (mbedTLS / TLS 1.3, network improvements).
3. .NET nanoFramework docs (System.Net / System.Net.Security).

---

Dependency version 1.11.46 does not exist on NuGet; package restore will fail.

The PR pins nanoFramework.System.Net to version 1.11.46, but this version does not appear to be published on NuGet — the latest listed release is 1.11.43 (published 2025-04-24). This will cause build failures when restoring dependencies. Verify the intended version: either revert to the latest published 1.11.43 or confirm 1.11.46 is a valid pre-release/private build and update accordingly.

🤖 Prompt for AI Agents

In nanoFramework.System.Net.Sockets.UdpClient/packages.lock.json around lines
23-28, the lock pins nanoFramework.System.Net to 1.11.46 which does not exist on
NuGet and will break restore; replace the resolved/requested version with the
latest published 1.11.43 (or the exact published version you intend to use),
regenerate the lock file (dotnet restore / update packages) so contentHash and
resolved entries are updated, or if 1.11.46 is a valid private/pre-release build
add the appropriate NuGet feed and authentication to the project feeds and CI
and then regenerate the lock file to reflect the private package metadata.