Update 4 NuGet dependencies

[nfbot]

Bumps nanoFramework.System.Net from 1.11.36 to 1.11.37
Bumps nanoFramework.System.Net.Http.Server from 1.5.187 to 1.5.188
Bumps nanoFramework.Json from 2.2.188 to 2.2.189
Bumps nanoFramework.System.Device.Wifi from 1.5.126 to 1.5.127

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated several dependency versions across the platform, including key components related to networking, HTTP handling, Wi-Fi connectivity, and JSON processing.
  • These upgrades help ensure consistency and reliability throughout both core functionalities and test suites.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This pull request updates the dependency versions in several packages.lock.json files across the repository. The changes bump the versions of nanoFramework.System.Net (from 1.11.36 to 1.11.37) and nanoFramework.System.Net.Http.Server (from 1.5.187 to 1.5.188) in both core and test files, with corresponding updates to their content hashes. In addition, the test files update the versions for nanoFramework.System.Device.Wifi and nanoFramework.Json to their respective newer releases.

Changes

File(s)	Summary
nanoFramework.WebServer.../packages.lock.json	Updated dependency versions for nanoFramework.System.Net (1.11.36 → 1.11.37) and nanoFramework.System.Net.Http.Server (1.5.187 → 1.5.188) with corresponding content hash updates.
tests/WebServerE2ETests/packages.lock.json	Updated nanoFramework.System.Device.Wifi from 1.5.126 to 1.5.127, along with updates for nanoFramework.System.Net (1.11.36 → 1.11.37) and nanoFramework.System.Net.Http.Server (1.5.187 → 1.5.188) and their hashes.
tests/nanoFramework.WebServer.Tests/packages.lock.json	Updated nanoFramework.Json from 2.2.188 to 2.2.189, in addition to updating nanoFramework.System.Net (1.11.36 → 1.11.37) and nanoFramework.System.Net.Http.Server (1.5.187 → 1.5.188) with new content hashes.

Possibly related PRs

• Update 1 NuGet dependencies #288: Updates the version of nanoFramework.System.Net and nanoFramework.System.Net.Http.Server, closely matching the dependency changes in this PR.
• Update 1 NuGet dependencies #279: Involves identical version updates for the same dependencies, indicating a strong code-level connection.
• Update 3 NuGet dependencies #291: Addresses direct code-level dependency version increments that align with the modifications made in this pull request.

---

📜 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 8184f9e and e19d0fc.

⛔ 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 (2 hunks)

---

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

🪧 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.
• @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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud