Update 4 NuGet dependencies

[nfbot]

Bumps nanoFramework.CoreLibrary from 1.15.5 to 1.16.1
Bumps nanoFramework.Logging from 1.1.125 to 1.1.127
Bumps nanoFramework.Runtime.Native from 1.7.1 to 1.7.7
Bumps nanoFramework.TestFramework from 3.0.49 to 3.0.57

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated dependency versions:
    • nanoFramework.CoreLibrary from 1.15.5 to 1.16.1
    • nanoFramework.TestFramework from 3.0.49 to 3.0.57
    • nanoFramework.Logging from 1.1.125 to 1.1.127
    • nanoFramework.Runtime.Native from 1.7.1 to 1.7.7

[coderabbitai]

Walkthrough

This pull request focuses on updating dependency versions across multiple project files. The changes primarily involve upgrading versions of core nanoFramework libraries such as nanoFramework.CoreLibrary, nanoFramework.TestFramework, nanoFramework.Logging, and nanoFramework.Runtime.Native in various packages.lock.json files. The updates span three different project configurations: NFUnitTestStringBuilder, System.Text.Benchmark, and System.Text.

Changes

File	Changes
Tests/NFUnitTestStringBuilder/packages.lock.json	- Updated nanoFramework.CoreLibrary from [1.15.5, 1.15.5] to [1.16.1, 1.16.1] - Updated nanoFramework.TestFramework from [3.0.49, 3.0.49] to [3.0.57, 3.0.57]
nanoFramework.System.Text.Benchmark/packages.lock.json	- Updated nanoFramework.CoreLibrary from 1.15.5 to 1.16.1 - Updated nanoFramework.Logging from 1.1.125 to 1.1.127 - Updated nanoFramework.Runtime.Native from 1.7.1 to 1.7.7
nanoFramework.System.Text/packages.lock.json	- Updated nanoFramework.CoreLibrary from 1.15.5 to 1.16.1

Possibly related PRs

• Update 1 NuGet dependencies #176: Updates nanoFramework.TestFramework from 2.1.113 to 3.0.42
• Update 1 NuGet dependencies #177: Updates nanoFramework.TestFramework from 3.0.42 to 3.0.47
• Update 2 NuGet dependencies #160: Updates nanoFramework.CoreLibrary in System.Text.Benchmark project

---

📜 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 15ee8de and 4750c5a.

⛔ Files ignored due to path filters (7)

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

📒 Files selected for processing (3)

• Tests/NFUnitTestStringBuilder/packages.lock.json (1 hunks)
• nanoFramework.System.Text.Benchmark/packages.lock.json (1 hunks)
• nanoFramework.System.Text/packages.lock.json (1 hunks)

🧰 Additional context used

🪛 GitHub Actions: PR Checks

nanoFramework.System.Text.Benchmark/packages.lock.json

[error] Package lock file needs to be updated to match the latest package versions

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

• GitHub Check: System.Text (Build_Library)

🔇 Additional comments (3)

nanoFramework.System.Text/packages.lock.json (1)

7-9: LGTM: CoreLibrary version update matches PR objectives.

The update of nanoFramework.CoreLibrary to version 1.16.1 is consistent with the PR objectives.

✅ Verification successful

✓ Verified: CoreLibrary v1.16.1 is available in NuGet

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify the version exists in NuGet
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.corelibrary/index.json | jq '.versions[] | select(. == "1.16.1")'

Length of output: 137

Tests/NFUnitTestStringBuilder/packages.lock.json (1)

7-9: LGTM: Version updates match PR objectives.

Both dependency updates are consistent with PR objectives:

• CoreLibrary: 1.15.5 → 1.16.1
• TestFramework: 3.0.49 → 3.0.57

Also applies to: 13-15

✅ Verification successful

✓ Verified: Package versions are valid and available

Both updated package versions exist in the NuGet registry:

• nanoFramework.CoreLibrary 1.16.1
• nanoFramework.TestFramework 3.0.57

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify versions exist in NuGet
echo "Verifying CoreLibrary 1.16.1..."
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.corelibrary/index.json | jq '.versions[] | select(. == "1.16.1")'

echo "Verifying TestFramework 3.0.57..."
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.testframework/index.json | jq '.versions[] | select(. == "3.0.57")'

Length of output: 427

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

13-15: LGTM: Version updates match PR objectives.

All three dependency updates are consistent with PR objectives:

• CoreLibrary: 1.15.5 → 1.16.1
• Logging: 1.1.125 → 1.1.127
• Runtime.Native: 1.7.1 → 1.7.7

Also applies to: 19-21, 25-27

✅ Verification successful

✓ Package versions verified in NuGet registry

All updated package versions exist in the NuGet registry and are available for use:

• nanoFramework.CoreLibrary 1.16.1
• nanoFramework.Logging 1.1.127
• nanoFramework.Runtime.Native 1.7.7

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Verify versions exist in NuGet
echo "Verifying CoreLibrary 1.16.1..."
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.corelibrary/index.json | jq '.versions[] | select(. == "1.16.1")'

echo "Verifying Logging 1.1.127..."
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.logging/index.json | jq '.versions[] | select(. == "1.1.127")'

echo "Verifying Runtime.Native 1.7.7..."
curl -s https://api.nuget.org/v3-flatcontainer/nanoframework.runtime.native/index.json | jq '.versions[] | select(. == "1.7.7")'

Length of output: 629

🧰 Tools

🪛 GitHub Actions: PR Checks

[error] Package lock file needs to be updated to match the latest package versions

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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