Update 1 NuGet dependencies

[nfbot]

Bumps nanoFramework.TestFramework from 3.0.75 to 3.0.77

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Chores
  • Updated the test framework dependency to a newer version for improved reliability.

[coderabbitai]

Walkthrough

The change updates the nanoFramework.TestFramework package version from 3.0.75 to 3.0.77 in the packages.lock.json file located in the Tests/SerializationTests directory. This update adjusts the requested version range, resolved version, and content hash for the package. No other dependencies or files were modified.

Changes

File(s)	Change Summary
Tests/SerializationTests/packages.lock.json	Updated nanoFramework.TestFramework package from 3.0.75 to 3.0.77.

---

📜 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 e2a2f9d and 3b3dff2.

⛔ Files ignored due to path filters (2)

• Tests/SerializationTests/SerializationTests.nfproj is excluded by none and included by none
• Tests/SerializationTests/packages.config is excluded by none and included by none

📒 Files selected for processing (1)

• Tests/SerializationTests/packages.lock.json (1 hunks)

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

• GitHub Check: nanoframework.System.Runtime.Serialization (Build Library Building Library)
• GitHub Check: nanoframework.System.Runtime.Serialization (Build Helper Building Helper)
• GitHub Check: nanoframework.System.Runtime.Serialization (Build preparations Running prep checks)

🔇 Additional comments (1)

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

13-15:

❓ Verification inconclusive

Version bump for nanoFramework.TestFramework in lock file

The update from 3.0.75 to 3.0.77 in packages.lock.json aligns the locked artifacts correctly. Please confirm that the corresponding PackageReference in your .csproj has also been updated to 3.0.77, otherwise a subsequent dotnet restore may revert this change.

Run this script to verify the project reference:

---

🏁 Script executed:

#!/bin/bash
# Verify that the TestFramework package reference in the csproj matches 3.0.77
find Tests/SerializationTests -maxdepth 1 -name "*.csproj" -print0 \
  | xargs -0 -n1 grep -H "<PackageReference.*Include=\"nanoFramework.TestFramework\".*Version=\"3.0.77\"" 

Length of output: 168

---

The initial check yielded no results (likely due to -maxdepth 1 or path differences). Let’s search all project files under Tests/SerializationTests for any TestFramework references:

---

🏁 Script executed:

#!/bin/bash
# Search all .csproj files under Tests/SerializationTests for nanoFramework.TestFramework references
find Tests/SerializationTests -type f -name "*.csproj" -print0 \
  | xargs -0 grep -H 'Include="nanoFramework.TestFramework"'

Length of output: 123

---

Let’s locate any .csproj under Tests/SerializationTests and inspect its PackageReference entries:

---

🏁 Script executed:

#!/bin/bash
# List all .csproj files under Tests/SerializationTests
find Tests/SerializationTests -type f -name "*.csproj" -print

# For each .csproj, show all PackageReference lines
grep -R -n "<PackageReference" Tests/SerializationTests

Length of output: 121

---

Let’s search the entire repo for any .csproj files and check for nanoFramework.TestFramework references:

---

🏁 Script executed:

#!/bin/bash
# List all .csproj files in the repo
echo "=== All .csproj files ==="
find . -type f -iname "*.csproj" -print

# Search those projects for the TestFramework reference
echo -e "\n=== PackageReference entries for nanoFramework.TestFramework ==="
find . -type f -iname "*.csproj" -print0 \
  | xargs -0 grep -H 'Include="nanoFramework.TestFramework"' || true

Length of output: 356

---

Verify TestFramework version bump in lock file and project reference

We’ve updated nanoFramework.TestFramework from 3.0.75 to 3.0.77 in Tests/SerializationTests/packages.lock.json. Since no .csproj was found under Tests/SerializationTests, please confirm that:

• Any TestFramework package reference in your project is also set to 3.0.77
• The lock file is in sync with your project’s PackageReference, to avoid dotnet restore reverting this change

You can double‑check with:

# Search entire repo for TestFramework references and versions
grep -R -n 'nanoFramework.TestFramework' .

---

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 generate sequence diagram to generate a sequence diagram of the changes in 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