Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.Benchmark from 1.0.112 to 1.0.113

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated benchmark framework dependency to the latest version.

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

[coderabbitai]

Walkthrough

Updates the nanoFramework.Benchmark dependency in the benchmarks project from version 1.0.112 to 1.0.113 in the packages.lock.json file, updating the resolved version, requested range, and content hash accordingly.

Changes

Cohort / File(s)	Summary
Dependency version bump nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json	Updates nanoFramework.Benchmark from 1.0.112 to 1.0.113 with corresponding contentHash update

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Update 2 NuGet dependencies #95: Updates the same nanoFramework.Benchmark entry in packages.lock.json to a different version
• Update 1 NuGet dependencies #89: Bumps nanoFramework.Benchmark dependency in the same packages.lock.json file
• Update 1 NuGet dependencies #86: Modifies the nanoFramework.Benchmark entry in packages.lock.json with a version upgrade

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 1 NuGet dependencies' accurately reflects the main change: bumping nanoFramework.Benchmark dependency from 1.0.112 to 1.0.113 in the packages.lock.json file.
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/af5b7076-e1d5-49bc-96fb-65afb79f3947

---

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0886cd3 and 5afb681.

⛔ 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)

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Dependency update looks good.

The version bump from 1.0.112 to 1.0.113 for nanoFramework.Benchmark is a patch-level update with the requested range, resolved version, and contentHash appropriately updated. Lock file structure and integrity are preserved.

To ensure the update is safe, please verify that version 1.0.113 of nanoFramework.Benchmark introduces only bug fixes and no breaking changes:

---

🌐 Web query:

nanoFramework.Benchmark 1.0.113 release notes changelog

💡 Result:

Do you mean the NuGet package nanoFramework.Benchmark version 1.0.113? I can't find a release or NuGet page for that exact version — should I (a) search GitHub and NuGet more deeply for 1.0.113, or (b) fetch the latest available Benchmark release notes instead?

---

Version 1.0.113 of nanoFramework.Benchmark cannot be found on NuGet.org

Web searches confirm that nanoFramework.Benchmark version 1.0.113 is not available on the NuGet package registry. The latest findable versions are significantly lower (1.0.71 and 1.0.97). The lock file references a version that doesn't appear to exist, which will cause restore failures.

Verify the correct version number—it may be a typo, pre-release version, or an unreleased version. If 1.0.112 is the current version, confirm whether you intended to target that instead or wait for 1.0.113 to be published.

🤖 Prompt for AI Agents

In nanoFramework.Hardware.Esp32.Rmt.Benchmarks/packages.lock.json around lines
7–9 the lock file references nanoFramework.Benchmark version 1.0.113 which does
not exist on NuGet; update the requested/resolved entry to a valid published
version (e.g., 1.0.112 or 1.0.97) or remove/regenerate the lock file to match
the project package reference. Verify the intended target in the project file
(csproj/PackageReference), correct any typo, then run a restore to regenerate
packages.lock.json so requested and resolved versions match a published NuGet
package; if 1.0.113 is intended, wait for it to be published before locking to
that version.

[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