Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Logging from 1.1.156 to 1.1.157

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the nanoFramework.Logging package to a newer version.

[coderabbitai]

Walkthrough

This change updates the nanoFramework.Logging package version in the nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json file from 1.1.156 to 1.1.157. The version range, resolved version, and content hash for this package were modified to match the new version. No other packages or metadata were changed, and there were no alterations to public or exported entities.

Changes

File(s)	Change Summary
nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json	Updated nanoFramework.Logging package version from 1.1.156 to 1.1.157, including version range, resolved version, and content hash.

Possibly related PRs

• Update 3 NuGet dependencies #85: Updates the nanoFramework.Logging package version in the packages.lock.json file, similar to this PR.
• Update 2 NuGet dependencies #79: Updates the nanoFramework.Logging package version in the same dependency file, directly related to this change.
• Update 1 NuGet dependencies #75: Also updates the nanoFramework.Logging package version in the packages.lock.json file, making it directly related.

---

📜 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 1f705d4 and e7e19bd.

⛔ Files ignored due to path filters (2)

• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/nanoFramework.Hardware.Esp32.Rmt.Benchmarks.nfproj is excluded by none and included by none
• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: nanoFramework / NuGets using latest version
• GitHub Check: Analyze (actions)

🔇 Additional comments (1)

nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json (1)

19-21:

✅ Verification successful

Automated lock file update for nanoFramework.Logging looks correct.
The requested, resolved, and contentHash fields have been consistently bumped from 1.1.156 to 1.1.157.

Please verify that the new version exists on NuGet and matches the provided hash:

---

🏁 Script executed:

#!/bin/bash
# Check that 1.1.157 is published
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.logging/index.json \
  | jq '.versions | index("1.1.157")'
# (Expect a non-null output)

# Optionally, confirm project files reference the new version
fd --extension csproj . | xargs rg -n '<PackageReference Include="nanoFramework.Logging" Version="1.1.157"'

Length of output: 231

---

Approve lock file bump to nanoFramework.Logging v1.1.157

The bump in nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json is correct:

• ✅ Confirmed nanoFramework.Logging 1.1.157 is published on NuGet (index 165).
• ✅ No direct <PackageReference> to v1.1.157 found in any .csproj files, which is expected since this change only affects the lock file.

No further changes required.

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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