Update 3 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.Net from 1.11.15 to 1.11.17
Bumps nanoFramework.System.Net.Http.Server from 1.5.162 to 1.5.165
Bumps nanoFramework.System.Device.Wifi from 1.5.105 to 1.5.107

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Updated nanoFramework.System.Net from version 1.11.15 to 1.11.17
  • Updated nanoFramework.System.Net.Http.Server from version 1.5.162 to 1.5.165
  • Updated nanoFramework.System.Device.Wifi from version 1.5.105 to 1.5.107

These updates affect multiple projects and test configurations, potentially bringing bug fixes and improvements to the nanoFramework WebServer ecosystem.

[coderabbitai]

Walkthrough

This pull request involves updating dependency versions across multiple packages.lock.json files in the nanoFramework WebServer project. The primary changes include version increments for nanoFramework.System.Net from 1.11.15 to 1.11.17 and nanoFramework.System.Net.Http.Server from 1.5.162 to 1.5.165. These updates affect the WebServer, FileSystem, and test projects, suggesting a coordinated dependency update across the project's components.

Changes

File	Change Summary
nanoFramework.WebServer.FileSystem/packages.lock.json	Updated nanoFramework.System.Net to 1.11.17 and nanoFramework.System.Net.Http.Server to 1.5.165
nanoFramework.WebServer/packages.lock.json	Updated nanoFramework.System.Net to 1.11.17 and nanoFramework.System.Net.Http.Server to 1.5.165
tests/WebServerE2ETests/packages.lock.json	Updated nanoFramework.System.Device.Wifi to 1.5.107, nanoFramework.System.Net to 1.11.17, and nanoFramework.System.Net.Http.Server to 1.5.165
tests/nanoFramework.WebServer.Tests/packages.lock.json	Updated nanoFramework.System.Net to 1.11.17 and nanoFramework.System.Net.Http.Server to 1.5.165

Possibly related PRs

• Update 3 NuGet dependencies #263: Updates the same dependencies in WebServer and FileSystem projects
• Update 1 NuGet dependencies #275: Updates nanoFramework.System.Net in WebServer Tests
• Update 5 NuGet dependencies #287: Similar dependency updates in WebServer and FileSystem projects

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 615f6e5 and 560e1b6.

⛔ Files ignored due to path filters (10)

• nanoFramework.WebServer.FileSystem.nuspec is excluded by none and included by none
• nanoFramework.WebServer.FileSystem/nanoFramework.WebServer.FileSystem.nfproj is excluded by none and included by none
• nanoFramework.WebServer.FileSystem/packages.config is excluded by none and included by none
• nanoFramework.WebServer.nuspec is excluded by none and included by none
• nanoFramework.WebServer/nanoFramework.WebServer.nfproj is excluded by none and included by none
• nanoFramework.WebServer/packages.config is excluded by none and included by none
• tests/WebServerE2ETests/WebServerE2ETests.nfproj is excluded by none and included by none
• tests/WebServerE2ETests/packages.config is excluded by none and included by none
• tests/nanoFramework.WebServer.Tests/nanoFramework.WebServer.Tests.nfproj is excluded by none and included by none
• tests/nanoFramework.WebServer.Tests/packages.config is excluded by none and included by none

📒 Files selected for processing (4)

• nanoFramework.WebServer.FileSystem/packages.lock.json (1 hunks)
• nanoFramework.WebServer/packages.lock.json (1 hunks)
• tests/WebServerE2ETests/packages.lock.json (2 hunks)
• tests/nanoFramework.WebServer.Tests/packages.lock.json (1 hunks)

🔇 Additional comments (4)

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

31-33: LGTM! Version updates are consistent.

The dependency updates for nanoFramework.System.Net (1.11.17) and nanoFramework.System.Net.Http.Server (1.5.165) are properly specified with exact version constraints and matching content hashes.

Also applies to: 37-39

tests/nanoFramework.WebServer.Tests/packages.lock.json (1)

37-39: LGTM! Test project dependencies are in sync.

The test project's dependency versions match the main project, maintaining consistency across the solution.

Also applies to: 43-45

nanoFramework.WebServer.FileSystem/packages.lock.json (1)

37-39: LGTM! FileSystem project dependencies are in sync.

The FileSystem project's dependency versions align with other projects in the solution.

Also applies to: 43-45

tests/WebServerE2ETests/packages.lock.json (1)

25-27: LGTM! E2E test project includes all dependency updates.

All three dependency updates are properly implemented:

• nanoFramework.System.Device.Wifi (1.5.107)
• nanoFramework.System.Net (1.11.17)
• nanoFramework.System.Net.Http.Server (1.5.165)

Also applies to: 43-45, 49-51

---

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.