Update 2 NuGet dependencies

[nfbot]

Bumps nanoFramework.Benchmark from 1.0.103 to 1.0.104
Bumps nanoFramework.Logging from 1.1.146 to 1.1.147

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Upgraded core dependency versions to the most recent stable releases, ensuring enhanced consistency and reliability throughout the system.
  • These updates improve overall system stability and lay a robust foundation for future enhancements, delivering a smoother and more dependable experience for users.

[coderabbitai]

Walkthrough

This pull request updates the dependency versions in the packages.lock.json file for the nanoFramework.System.Text.RegularExpression.Benchmark project. Specifically, the nanoFramework.Benchmark dependency is updated from version 1.0.103 to 1.0.104 and the nanoFramework.Logging dependency is updated from version 1.1.146 to 1.1.147. The corresponding contentHash values are updated to reflect these changes without altering other file structures.

Changes

File	Change Summary
nanoFramework.../packages.lock.json	Updated nanoFramework.Benchmark from [1.0.103, 1.0.103]/1.0.103 to [1.0.104, 1.0.104]/1.0.104 and nanoFramework.Logging from [1.1.146, 1.1.146]/1.1.146 to [1.1.147, 1.1.147]/1.1.147; content hashes updated.

Possibly related PRs

• Update 1 NuGet dependencies #108: Updates the nanoFramework.Benchmark dependency with different version changes, showing a direct code-level link.
• Update 2 NuGet dependencies #106: Involves modifications to both nanoFramework.Benchmark and nanoFramework.Logging in the packages.lock.json file, aligning with the current changes.
• Update 2 NuGet dependencies #100: Contains updates to the same dependencies (nanoFramework.Benchmark and nanoFramework.Logging) in the packages.lock.json, indicating a direct connection at the code level.

---

📜 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 4b10f67 and a1d630c.

⛔ Files ignored due to path filters (2)

• nanoFramework.System.Text.RegularExpression.Benchmark/nanoFramework.System.Text.RegularExpression.Benchmark.nfproj is excluded by none and included by none
• nanoFramework.System.Text.RegularExpression.Benchmark/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• nanoFramework.System.Text.RegularExpression.Benchmark/packages.lock.json (2 hunks)

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

• GitHub Check: nanoFramework / NuGets using latest version

🔇 Additional comments (2)

nanoFramework.System.Text.RegularExpression.Benchmark/packages.lock.json (2)

7-9: Dependency Version Update for nanoFramework.Benchmark is Correct

The update correctly changes the requested field from [1.0.103, 1.0.103] to [1.0.104, 1.0.104] and the resolved field from "1.0.103" to "1.0.104". The updated contentHash confirms that the change is consistent with the new dependency version.

---

19-21: Dependency Version Update for nanoFramework.Logging is Correct

The version update for nanoFramework.Logging is properly reflected with the requested field changing to [1.1.147, 1.1.147] and the resolved field updating to "1.1.147", alongside the new contentHash. This aligns perfectly with the PR objectives for updating the package version.

---

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