Update 11 NuGet dependencies

[nfbot]

Bumps nanoFramework.Iot.Device.Button from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Ws28xx.Esp32 from 1.2.696 to 1.2.737
Bumps Nerdbank.GitVersioning from 3.7.112 to 3.7.115
Bumps nanoFramework.Iot.Device.Mpu6886 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Buzzer from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.ePaper from 1.0.558 to 1.0.573
Bumps nanoFramework.Iot.Device.Rtc from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Bmm150 from 1.2.704 to 1.2.737
Bumps nanoFramework.Iot.Device.Ip5306 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Axp192 from 1.2.718 to 1.2.737
Bumps nanoFramework.Iot.Device.Chsc6540 from 1.1.696 to 1.1.737

[version update]

⚠️ This is an automated update. ⚠️

Summary by CodeRabbit

• Dependency Updates
  • Multiple nanoFramework IoT device dependencies updated across various projects
  • Versions upgraded from 1.2.718 to 1.2.737 for most device libraries
  • Nerdbank.GitVersioning updated from 3.7.112 to 3.7.115
  • Consistent version increments across different device libraries and test applications

[coderabbitai]

Walkthrough

This pull request involves a comprehensive update of dependency versions across multiple packages.lock.json files in various nanoFramework projects. The updates primarily focus on incrementing versions of IoT device-related dependencies and the Nerdbank.GitVersioning tool. Most dependencies are being upgraded from versions around 1.2.718 to 1.2.737, with some specific variations depending on the project.

Changes

File Path	Change Summary
Tests/*/packages.lock.json	Updated multiple IoT device dependencies (Button, Ws28xx, Bmm150, Mpu6886, etc.) from versions like 1.2.718 to 1.2.737
nanoFramework.*/packages.lock.json	Similar dependency updates across different project configurations, including Nerdbank.GitVersioning from 3.7.112 to 3.7.115

Possibly related PRs

• Update 5 NuGet dependencies #331: Updates nanoFramework.Iot.Device.Button dependency
• Update 14 NuGet dependencies #333: Updates nanoFramework.Iot.Device.Button and nanoFramework.Iot.Device.Ws28xx.Esp32
• Update 4 NuGet dependencies #334: Updates nanoFramework.Iot.Device.Ws28xx.Esp32
• Update 7 NuGet dependencies #368: Includes updates to nanoFramework.System.Text

Suggested Labels

CI: Publish Release

Suggested Reviewers

• Ellerbach

---

📜 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 72ee5af and eae378c.

⛔ Files ignored due to path filters (41)

• Tests/AtomLiteTestApp/AtomLiteTestApp.nfproj is excluded by none and included by none
• Tests/AtomLiteTestApp/packages.config is excluded by none and included by none
• Tests/AtomMatrixTestApp/AtomMatrixTestApp.nfproj is excluded by none and included by none
• Tests/AtomMatrixTestApp/packages.config is excluded by none and included by none
• Tests/FireTestApp/FireTestApp.nfproj is excluded by none and included by none
• Tests/FireTestApp/packages.config is excluded by none and included by none
• Tests/M5Core2TestApp/M5Core2TestApp.nfproj is excluded by none and included by none
• Tests/M5Core2TestApp/packages.config is excluded by none and included by none
• Tests/M5CoreTestApp/M5CoreTestApp.nfproj is excluded by none and included by none
• Tests/M5CoreTestApp/packages.config is excluded by none and included by none
• Tests/M5StickTestApp/M5StickTestApp.nfproj is excluded by none and included by none
• Tests/M5StickTestApp/packages.config is excluded by none and included by none
• Tests/ToughTestApp/ToughTestApp.nfproj is excluded by none and included by none
• Tests/ToughTestApp/packages.config is excluded by none and included by none
• nanoFramework.AtomLite.nuspec is excluded by none and included by none
• nanoFramework.AtomLite/nanoFramework.AtomLite.nfproj is excluded by none and included by none
• nanoFramework.AtomLite/packages.config is excluded by none and included by none
• nanoFramework.AtomMatrix.nuspec is excluded by none and included by none
• nanoFramework.AtomMatrix/nanoFramework.AtomMatrix.nfproj is excluded by none and included by none
• nanoFramework.AtomMatrix/packages.config is excluded by none and included by none
• nanoFramework.CoreInk.nuspec is excluded by none and included by none
• nanoFramework.CoreInk/nanoFramework.CoreInk.nfproj is excluded by none and included by none
• nanoFramework.CoreInk/packages.config is excluded by none and included by none
• nanoFramework.Fire.nuspec is excluded by none and included by none
• nanoFramework.Fire/nanoFramework.Fire.nfproj is excluded by none and included by none
• nanoFramework.Fire/packages.config is excluded by none and included by none
• nanoFramework.M5Core.nuspec is excluded by none and included by none
• nanoFramework.M5Core/nanoFramework.M5Core.nfproj is excluded by none and included by none
• nanoFramework.M5Core/packages.config is excluded by none and included by none
• nanoFramework.M5Core2.nuspec is excluded by none and included by none
• nanoFramework.M5Core2/nanoFramework.M5Core2.nfproj is excluded by none and included by none
• nanoFramework.M5Core2/packages.config is excluded by none and included by none
• nanoFramework.M5StickC.nuspec is excluded by none and included by none
• nanoFramework.M5StickC/nanoFramework.M5StickC.nfproj is excluded by none and included by none
• nanoFramework.M5StickC/packages.config is excluded by none and included by none
• nanoFramework.M5StickCPlus.nuspec is excluded by none and included by none
• nanoFramework.M5StickCPlus/nanoFramework.M5StickCPlus.nfproj is excluded by none and included by none
• nanoFramework.M5StickCPlus/packages.config is excluded by none and included by none
• nanoFramework.Tough.nuspec is excluded by none and included by none
• nanoFramework.Tough/nanoFramework.Tough.nfproj is excluded by none and included by none
• nanoFramework.Tough/packages.config is excluded by none and included by none

📒 Files selected for processing (16)

• Tests/AtomLiteTestApp/packages.lock.json (1 hunks)
• Tests/AtomMatrixTestApp/packages.lock.json (1 hunks)
• Tests/FireTestApp/packages.lock.json (1 hunks)
• Tests/M5Core2TestApp/packages.lock.json (2 hunks)
• Tests/M5CoreTestApp/packages.lock.json (1 hunks)
• Tests/M5StickTestApp/packages.lock.json (2 hunks)
• Tests/ToughTestApp/packages.lock.json (1 hunks)
• nanoFramework.AtomLite/packages.lock.json (2 hunks)
• nanoFramework.AtomMatrix/packages.lock.json (2 hunks)
• nanoFramework.CoreInk/packages.lock.json (3 hunks)
• nanoFramework.Fire/packages.lock.json (2 hunks)
• nanoFramework.M5Core/packages.lock.json (2 hunks)
• nanoFramework.M5Core2/packages.lock.json (3 hunks)
• nanoFramework.M5StickC/packages.lock.json (3 hunks)
• nanoFramework.M5StickCPlus/packages.lock.json (3 hunks)
• nanoFramework.Tough/packages.lock.json (3 hunks)

🔇 Additional comments (17)

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

25-27: LGTM! Version updates are consistent.

The dependency updates align with the PR objectives and maintain version consistency across the project.

Also applies to: 31-33

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

25-27: LGTM! Version updates maintain consistency.

The dependency updates match those in AtomLiteTestApp, ensuring consistency across test applications.

Also applies to: 31-33

nanoFramework.AtomLite/packages.lock.json (1)

31-33: LGTM! Version updates are appropriate.

The dependency updates align with the PR objectives. The Nerdbank.GitVersioning update is a minor tooling change.

Let's verify if there are any known issues with these versions:

Also applies to: 37-39, 79-81

✅ Verification successful

Version updates are consistent and properly applied

All IoT Device packages are consistently updated to version 1.2.737 across all projects, with proper version locking and resolution. The changes are well-coordinated and maintain dependency consistency.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Check for any reported issues in the repository related to these versions
gh issue list --search "in:title 1.2.737 OR 3.7.115" --state all --limit 5

Length of output: 149

---

Script:

#!/bin/bash
# Check for version references in configuration files
fd -e json -e config -e props -e csproj | xargs rg "1\.2\.737|version" -A 2 -B 2

# Also check for any package reference entries
fd -e csproj | xargs rg "<PackageReference.*?>" -A 1

Length of output: 67113

nanoFramework.AtomMatrix/packages.lock.json (1)

31-33: LGTM! Version updates maintain consistency.

All dependency updates align with the PR objectives and maintain version consistency across the project.

Also applies to: 37-39, 43-45, 109-111

nanoFramework.CoreInk/packages.lock.json (1)

25-27: LGTM! Version updates are consistent and appropriate.

All dependency updates align with the PR objectives. The ePaper package follows a different versioning scheme but still represents a minor update.

Also applies to: 31-33, 43-45, 49-51, 109-111

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

25-33: LGTM! Consistent version updates across IoT device packages.

The updates to nanoFramework.Iot.Device.* packages (Axp192, Chsc6540) from version 1.2.718/1.1.696 to 1.2.737/1.1.737 are consistent with the changes across other files in this PR.

Also applies to: 31-33, 37-39

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

31-33: LGTM! Consistent version updates for M5StickTestApp dependencies.

The updates to IoT device packages (Axp192, Button, Mpu6886, Rtc) from version 1.2.718 to 1.2.737 maintain consistency with other test applications.

Also applies to: 37-39, 49-51, 55-57

nanoFramework.M5StickC/packages.lock.json (1)

31-33: LGTM! Version updates include both IoT packages and build tools.

The changes include:

1. IoT device packages updated to version 1.2.737
2. Nerdbank.GitVersioning updated from 3.7.112 to 3.7.115

Also applies to: 37-39, 49-51, 55-57, 127-129

nanoFramework.Tough/packages.lock.json (1)

31-33: Verify the impact of these dependency updates.

While the version updates look consistent, since these are IoT device packages that interact with hardware, it's recommended to verify:

1. Any breaking changes in the updated versions
2. Hardware compatibility with the new versions
3. Impact on device communication and functionality

Run the following script to check for any breaking changes or compatibility notes:

Also applies to: 37-39, 49-51, 145-147

✅ Verification successful

Dependency updates verified - no breaking changes

These are routine NuGet dependency updates with no breaking changes or hardware compatibility issues documented. The changelog shows only maintenance updates and documentation improvements.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for breaking changes or compatibility notes in recent commits

# Check commit messages and PR descriptions for breaking changes
gh pr view 369 --json body | jq -r '.body' | grep -i "break\|compatibility\|impact"

# Search for BREAKING CHANGE or compatibility notes in recent commits
for pkg in "nanoFramework.Iot.Device.Axp192" "nanoFramework.Iot.Device.Button" "nanoFramework.Iot.Device.Mpu6886" "nanoFramework.Iot.Device.Rtc" "Nerdbank.GitVersioning"; do
  echo "Checking $pkg:"
  gh search commits --repo=nanoframework/nanoFramework.IoT.Device --match=commit "BREAKING CHANGE OR compatibility in:commit" --limit 10
done

Length of output: 10091

---

Script:

#!/bin/bash
# Search for changelog files and version documentation
echo "=== Searching for changelog and release notes ==="
fd -i "changelog|release.?notes|breaking.?changes" --type f

echo -e "\n=== Searching for version-specific content ==="
rg -i "version (1\.2\.737|compatibility|requirement)" -g "!{*.json,*.lock}"

echo -e "\n=== Searching for hardware compatibility info ==="
rg -i "(hardware|device).{0,30}(compatibility|requirement|support)" -g "!{*.json,*.lock}"

echo -e "\n=== Checking documentation for these specific packages ==="
rg -i "(axp192|button|mpu6886|rtc).{0,50}(breaking|compatibility|requirement)" -g "!{*.json,*.lock}"

Length of output: 813

---

Script:

#!/bin/bash
echo "=== Checking CHANGELOG.md content ==="
cat CHANGELOG.md

echo -e "\n=== Checking version requirements ==="
rg -A 2 -B 2 "\"version\":|\"requested\":|\"resolved\":" packages.lock.json

echo -e "\n=== Checking for dependency configurations ==="
fd -e json -e config -e props --exec cat {} \; | rg -i "(dependencyversion|packageversion|framework|runtime).{0,50}(requirement|version|compatibility)"

Length of output: 66142

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

19-21: LGTM! Consistent version updates for M5CoreTestApp dependencies.

The updates to IoT device packages (Bmm150, Button, Ip5306, Mpu6886) from version 1.2.718/1.2.704 to 1.2.737 align with the global version update strategy in this PR.

Also applies to: 25-27, 31-33, 37-39

nanoFramework.M5StickCPlus/packages.lock.json (1)

31-33: LGTM! Consistent version updates across IoT device packages.

The changes update multiple IoT device packages to version 1.2.737 and Nerdbank.GitVersioning to 3.7.115, maintaining consistency across the project dependencies.

Also applies to: 37-39, 43-45, 49-51, 55-57, 61-63, 139-141

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

31-33: LGTM! Consistent version updates for test app dependencies.

The changes update all IoT device packages to version 1.2.737, maintaining consistency with the main project dependencies.

Also applies to: 37-39, 43-45, 49-51, 55-57, 61-63

nanoFramework.M5Core/packages.lock.json (1)

25-27: LGTM! Consistent version updates for M5Core dependencies.

The changes update all IoT device packages to version 1.2.737 and Nerdbank.GitVersioning to 3.7.115, maintaining consistency across the project.

Also applies to: 31-33, 37-39, 43-45, 49-51, 175-177

nanoFramework.Fire/packages.lock.json (1)

37-39: LGTM! Consistent version updates for Fire project dependencies.

The changes update all IoT device packages to version 1.2.737 and Nerdbank.GitVersioning to 3.7.115, maintaining consistency across the project.

Also applies to: 43-45, 49-51, 55-57, 61-63, 67-69, 187-189

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

25-27: LGTM! Consistent version updates for M5Core2 test app dependencies.

The changes update all IoT device packages to version 1.2.737, maintaining consistency with the main project dependencies.

Also applies to: 31-33, 37-39, 49-51, 55-57

nanoFramework.M5Core2/packages.lock.json (2)

31-33: LGTM! Coordinated update of IoT device packages.

The IoT device packages have been consistently updated from their previous versions to 1.2.737, maintaining version alignment across the dependencies.

Also applies to: 37-39, 43-45, 61-63, 67-69

---

199-201: Verify compatibility with the updated Nerdbank.GitVersioning.

The build tool has been updated to version 3.7.115. Since this is a patch version update, it should maintain backward compatibility.

Run this script to check for any reported issues with the new version:

✅ Verification successful

✓ Nerdbank.GitVersioning 3.7.115 compatibility verified

The update is a patch version that maintains backward compatibility. No issues or compatibility problems were found for this version.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for known issues with Nerdbank.GitVersioning 3.7.115

# Check for any GitHub issues mentioning compatibility problems
gh api graphql -f query='
{
  search(query: "repo:dotnet/Nerdbank.GitVersioning is:issue state:open 3.7.115", type: ISSUE, first: 5) {
    nodes {
      ... on Issue {
        title
        url
        labels(first: 5) {
          nodes {
            name
          }
        }
      }
    }
  }
}'

# Check if the version exists in NuGet
curl -s "https://api.nuget.org/v3-flatcontainer/nerdbank.gitversioning/3.7.115/nerdbank.gitversioning.nuspec"

Length of output: 1681

---

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.