Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Logging from 1.1.113 to 1.1.120

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the nanoFramework.Logging dependency version from 1.1.113 to 1.1.120.

[coderabbitai]

Walkthrough

The changes in this pull request involve updating the dependency version for nanoFramework.Logging in the nanoFramework.Benchmark/packages.lock.json file. The version has been changed from 1.1.113 to 1.1.120, with corresponding updates to the requested, resolved, and contentHash fields for this dependency. No other dependencies in the file have been altered.

Changes

File Path	Change Summary
nanoFramework.Benchmark/packages.lock.json	Updated nanoFramework.Logging version from 1.1.113 to 1.1.120, modified requested, resolved, and contentHash fields accordingly.

Possibly related PRs

• Update 1 NuGet dependencies #36: This PR updates the nanoFramework.Logging package from 1.1.76 to 1.1.100, which is directly related to the changes in the main PR that update nanoFramework.Logging from 1.1.113 to 1.1.120.
• Update 1 NuGet dependencies #39: This PR updates the nanoFramework.Logging package from 1.1.100 to 1.1.107, showing a direct progression in the versioning of the same dependency.
• Update 1 NuGet dependencies #40: This PR updates the nanoFramework.Logging package from 1.1.107 to 1.1.108, continuing the version updates for the same dependency.
• Update 1 NuGet dependencies #44: This PR updates the nanoFramework.Logging package from 1.1.108 to 1.1.113, which is a direct predecessor to the version change in the main PR.

Suggested labels

CI: Publish Release

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 0e89e33 and 0b4efd8.

⛔ Files ignored due to path filters (3)

• nanoFramework.Benchmark.nuspec is excluded by none and included by none
• nanoFramework.Benchmark/nanoFramework.Benchmark.nfproj is excluded by none and included by none
• nanoFramework.Benchmark/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.Benchmark/packages.lock.json (1 hunks)

🔇 Additional comments (1)

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

13-15: LGTM! Verify changelog for breaking changes.

The version update follows the correct format and maintains consistency between requested and resolved versions. Since this is a minor version update (1.1.113 → 1.1.120), it should maintain backward compatibility.

Let's verify the changelog and potential breaking changes:

✅ Verification successful

Version update looks safe to proceed

The version jump from 1.1.113 to 1.1.120 shows no breaking changes or deprecation notices in the commit history. Both versions follow semantic versioning with only patch-level changes (1.1.x), indicating backward compatibility is maintained.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check the changelog and release notes for nanoFramework.Logging between versions 1.1.113 and 1.1.120

# Fetch release information for the version range
gh release list --repo nanoframework/nanoFramework.Logging \
  --limit 10 | grep -E "v1\.1\.(11[3-9]|120)"

# Check for breaking changes or deprecation notices in recent commits
gh api repos/nanoframework/nanoFramework.Logging/commits \
  --jq '.[] | select(.commit.message | test("break|deprecat|remove"; "i")) | {sha: .sha, message: .commit.message}' \
  | jq -c .

Length of output: 433

---

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 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.