Update 2 NuGet dependencies

[nfbot]

Bumps nanoFramework.Benchmark from 1.0.109 to 1.0.112
Bumps nanoFramework.Logging from 1.1.160 to 1.1.161

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated dependencies to latest stable versions: nanoFramework.Benchmark and nanoFramework.Logging.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updates two NuGet package dependencies in the benchmark project's lock file: nanoFramework.Benchmark upgraded from 1.0.109 to 1.0.112, and nanoFramework.Logging upgraded from 1.1.160 to 1.1.161. Content hashes updated accordingly.

Changes

Cohort / File(s)	Summary
Dependency version updates nanoFramework.Json.Benchmark/packages.lock.json	Updated nanoFramework.Benchmark from version 1.0.109 to 1.0.112 with new contentHash; updated nanoFramework.Logging from version 1.1.160 to 1.1.161 with new contentHash

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Verify version numbers are intentional and compatible with the benchmark project

Possibly related PRs

• nanoFramework.Json#412 — Modifies the same packages.lock.json entries for both nanoFramework.Benchmark and nanoFramework.Logging with version updates and contentHash changes
• nanoFramework.Json#428 — Updates the nanoFramework.Logging dependency entry in the same lock file
• nanoFramework.Json#374 — Updates the nanoFramework.Benchmark dependency version in packages.lock.json

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 accurately summarizes the main change: updating 2 NuGet dependencies (nanoFramework.Benchmark and nanoFramework.Logging).
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/20e9d31e-f2d1-4ffb-818c-e7cd86ab0749

---

📜 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 e90a2a0 and 5e82276.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (1)

• nanoFramework.Json.Benchmark/packages.lock.json (2 hunks)

🔇 Additional comments (2)

nanoFramework.Json.Benchmark/packages.lock.json (2)

7-9: Lock file updates verified and safe.

Both package versions exist on NuGet: nanoFramework.Benchmark 1.0.112 and nanoFramework.Logging 1.1.161. No security advisories found for either version. The lock file format is correct with properly formatted content hashes for reproducibility. Patch-level updates present minimal risk.

---

19-21: Content hash verification inconclusive; security status clean.

No public security advisories or CVEs were found for nanoFramework.Logging 1.1.161. The package exists on NuGet with expected metadata. However, the sandbox environment prevents direct hash validation. Verify the content hash locally or through your CI/CD pipeline using the NuGet package tooling if hash integrity verification is a requirement for your deployment process.

---

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

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