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 benchmark and logging dependencies to latest available versions.

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

[coderabbitai]

Walkthrough

Two direct NuGet package dependencies in the benchmark project lockfile are bumped: nanoFramework.Benchmark from 1.0.109 to 1.0.112 and nanoFramework.Logging from 1.1.160 to 1.1.161. Version numbers and content hashes are updated; no structural or logical changes.

Changes

Cohort / File(s)	Summary
Dependency version updates nanoFramework.MessagePack.Benchmark/packages.lock.json	Bumps nanoFramework.Benchmark to 1.0.112 and nanoFramework.Logging to 1.1.161; updates resolved versions and contentHash values

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Lockfile updates are mechanical changes with no logic or API surface modifications; verification requires only checking that version numbers and hashes are consistent and versions exist in the package registry.

Possibly related PRs

• Update 1 NuGet dependencies #13 — Sequential update to nanoFramework.Logging dependency in the same lockfile; both PRs follow a similar pattern of version bumping.

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 'Update 2 NuGet dependencies' directly and accurately describes the main change: bumping two NuGet package versions in the lockfile.
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/6fb74f19-526c-4289-8dff-0f97b87d7735

---

📜 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 d5da468 and 9a3415c.

⛔ Files ignored due to path filters (2)

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

📒 Files selected for processing (1)

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

🔇 Additional comments (2)

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

7-9: Approve nanoFramework.Benchmark update to 1.0.112.

The version increment from 1.0.109 to 1.0.112 is a patch-level update. The contentHash is updated appropriately for the new version.

Please verify that nanoFramework.Benchmark 1.0.112 has no known security vulnerabilities and is stable.

---

25-27: Approve nanoFramework.Logging update to 1.1.161.

The version increment from 1.1.160 to 1.1.161 is a patch-level update. The contentHash is updated appropriately for the new version.

Please verify that nanoFramework.Logging 1.1.161 has no known security vulnerabilities and is stable.

---

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

[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