Skip to content

Conversation

@nfbot
Copy link
Member

@nfbot nfbot commented Nov 19, 2025

Bumps nanoFramework.System.Net from 1.11.46 to 1.11.47

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

  • Chores
    • Updated project dependencies to compatible versions.

Bumps nanoFramework.System.Net from 1.11.46 to 1.11.47</br>
[version update]

### ⚠️ This is an automated update. ⚠️
@coderabbitai
Copy link

coderabbitai bot commented Nov 19, 2025

Walkthrough

Updated the nanoFramework.System.Net dependency from version 1.11.46 to 1.11.47 across two packages.lock.json files, including corresponding contentHash updates. No functional code changes.

Changes

Cohort / File(s) Summary
Dependency version bumps
Tests/packages.lock.json, nanoframework.System.Net.Sockets.TcpClient/packages.lock.json
Bumped nanoFramework.System.Net from 1.11.46 to 1.11.47 with updated contentHash values

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Simple, mechanical dependency version updates with matching contentHash changes across two lock files
  • No logic changes, functional code modifications, or complex interactions introduced

Possibly related PRs

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 summarizes the main change, which is updating the nanoFramework.System.Net dependency from version 1.11.46 to 1.11.47 across multiple package lock files.
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/1c4c4c07-8240-44b0-9166-394e0a9a27f4

📜 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 daaf4e6 and 254c932.

⛔ Files ignored due to path filters (5)
  • Tests/Tests.nfproj is excluded by none and included by none
  • Tests/packages.config is excluded by none and included by none
  • nanoframework.System.Net.Sockets.TcpClient.nuspec is excluded by none and included by none
  • nanoframework.System.Net.Sockets.TcpClient/nanoframework.System.Net.Sockets.TcpClient.nfproj is excluded by none and included by none
  • nanoframework.System.Net.Sockets.TcpClient/packages.config is excluded by none and included by none
📒 Files selected for processing (2)
  • Tests/packages.lock.json (1 hunks)
  • nanoframework.System.Net.Sockets.TcpClient/packages.lock.json (1 hunks)
🔇 Additional comments (2)
nanoframework.System.Net.Sockets.TcpClient/packages.lock.json (1)

23-28: Dependency update is consistent across both lock files.

The nanoFramework.System.Net upgrade from 1.11.46 to 1.11.47 is applied consistently in both packages.lock.json files with matching contentHashes, ensuring reproducible builds across test and product code.

Tests/packages.lock.json (1)

23-28: nanoFramework.System.Net 1.11.47 verified as valid.

Version 1.11.47 is officially released as of November 19, 2025, and the single change is a revert of a workaround for unintentional reset on UpdateConfiguration, indicating no breaking changes. The dependency update is properly formatted with appropriate version pinning for reproducible builds.


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

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

@nfbot nfbot merged commit 0efe4da into main Nov 19, 2025
8 checks passed
@nfbot nfbot deleted the nfbot/update-dependencies/1c4c4c07-8240-44b0-9166-394e0a9a27f4 branch November 19, 2025 10:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants