Update nbgv to 3.7.112

[josesimoes]

Description

Motivation and Context

How Has This Been Tested?

Screenshots

Types of changes

• Improvement (non-breaking change that improves a feature, code or algorithm)
• Bug fix (non-breaking change which fixes an issue with code or algorithm)
• New feature (non-breaking change which adds functionality to code)
• Breaking change (fix or feature that would cause existing functionality to change)
• Config and build (change in the configuration and build system, has no impact on code or features)
• Dependencies (update dependencies and changes associated, has no impact on code or features)
• Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• My code follows the code style of this project (only if there are changes in source code).
• My changes require an update to the documentation (there are changes that require the docs website to be updated).
• I have updated the documentation accordingly (the changes require an update on the docs in this repo).
• I have read the CONTRIBUTING document.
• I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
• I have added new tests to cover my changes.

Summary by CodeRabbit

• Bug Fixes
  • Updated the dependency version for Nerdbank.GitVersioning to enhance stability and performance.
• Chores
  • Modified version details in the package lock files for consistency across different frameworks.

[coderabbitai]

Warning

Rate limit exceeded

@josesimoes has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 56 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between ef55efa and 3054ae3.

⛔ Files ignored due to path filters (3)

• source/TestAdapter/nanoFramework.TestAdapter.csproj is excluded by none and included by none
• source/TestFramework/nanoFramework.TestFramework.nfproj is excluded by none and included by none
• source/TestFramework/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• source/TestAdapter/packages.lock.json (2 hunks)
• source/TestFramework/packages.lock.json (1 hunks)

Walkthrough

This pull request updates the Nerdbank.GitVersioning dependency version in two packages.lock.json files. The version is upgraded from 3.6.146 to 3.7.112 in both the TestAdapter and TestFramework project configurations. The changes include updates to the requested version range, resolved version, and the corresponding content hash for the dependency.

Changes

File	Change Summary
source/TestAdapter/packages.lock.json	Updated Nerdbank.GitVersioning dependency version from 3.6.146 to 3.7.112
source/TestFramework/packages.lock.json	Updated Nerdbank.GitVersioning dependency version from 3.6.146 to 3.7.112

Possibly related PRs

• Update 1 NuGet dependencies #260: Updates the Nerdbank.GitVersioning dependency in the source/TestFramework/packages.lock.json file, which is directly related to the current dependency version upgrade.

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

source/TestAdapter/packages.lock.json (1)

49-51: Version update is consistent across target frameworks!

The Nerdbank.GitVersioning package has been correctly updated to version 3.7.112 in both target frameworks (.NET Framework 4.8 and .NET 6.0).

Consider aligning version constraints

The version constraint in TestAdapter ([3.7.112, )) differs from TestFramework ([3.7.112, 3.7.112]). Consider using the same version constraint across both projects to prevent potential version mismatches in the future.

- "requested": "[3.7.112, )",
+ "requested": "[3.7.112, 3.7.112]",

Also applies to: 193-195

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 097d83f and cafe0ee.

⛔ Files ignored due to path filters (2)

• source/TestAdapter/nanoFramework.TestAdapter.csproj is excluded by none and included by none
• source/TestFramework/packages.config is excluded by none and included by none

📒 Files selected for processing (2)

• source/TestAdapter/packages.lock.json (2 hunks)
• source/TestFramework/packages.lock.json (1 hunks)

🔇 Additional comments (1)

source/TestFramework/packages.lock.json (1)

13-15: Version update looks good!

The Nerdbank.GitVersioning package has been correctly updated to version 3.7.112 with matching requested and resolved versions.